Skip to content

move error codes into visitor classes #82

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

Merged
merged 1 commit into from
Dec 19, 2022

Conversation

jakkdl
Copy link
Member

@jakkdl jakkdl commented Dec 16, 2022

also changes test_113 and 114_options to use ARGS (since they broke from this it was a good opportunity to rewrite them).

As a follow-up, it'd be nice for each visitor class to have a docstring briefly explaining what they do - just copying the relevant line from the readme would be plenty.

Yeah this has been sorely needed for a while, I started copy-pasting but started feeling very silly about it so the visitor classes now define their error codes themselves.
Would be fun to move the documentation from the readme into them and auto-generate docs (+ the same for command line args) as well, but that's probs overkill - although having to keep documentation correct in several different files & places is always a pain.

…. Change test_113 and 114_options to use ARGS
Copy link
Member

@Zac-HD Zac-HD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@Zac-HD Zac-HD merged commit 01cc0b1 into python-trio:main Dec 19, 2022
@jakkdl jakkdl deleted the move_error_message branch December 31, 2022 13:06
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.

2 participants