Skip to content

feature: add error_table in log file #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

timdegroot1996
Copy link

@timdegroot1996 timdegroot1996 commented Jun 15, 2025

Description

Provide a clear description of the changes introduced in this pull request.

Type of Change

  • Bug fix
  • New feature
  • Documentation update
  • Other (please describe below this line)

Checklist

  • I have run pylint and pyright and ensured my code follows the style guide.
  • I have added tests that prove my fix is effective or that my feature works.
  • I have commented my code where necessary
  • I have updated relevant documentation (README, changelog, etc.)

Test Coverage (optional)

Describe how the code was tested. Include the commands you ran or output, if relevant.

I could not get the unit tests to run, so if those could be run that would be helpful!

I ran the robot tests and added some .git-keep files for missing folders. I'm assuming these were missing and causing my tests to fail. If not they can be removed, along with the folders that I added to pass the integration tests.

Related Issue (optional)

If this PR fixes an issue, reference it here. Example: Closes #123.

Changelog (optional)

Should this PR be mentioned in the changelog? If yes, what should be the entry?

Addition of a filterable error table in the log file.

Additional Notes (optional)

Add any additional notes or context here.

Steps that I did not do (yet) that I might need help with:

  1. Review of the current pull request and implementation
  2. Run of the unit tests
  3. Some guidance of what/where the integration/unit tests should be updated (but as I haven't figured out the running part this might be tricky)
  4. Some guidance on what should be added to the readme (images, examples etc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant