-
Notifications
You must be signed in to change notification settings - Fork 6
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
Validate gh-issue is int before checking range, and that gh-issue or bpo exists #35
Conversation
Invalid GitHub issue number! ('one-two') instead of: ValueError: invalid literal for int() with base 10: 'one-two'
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
), | ||
( | ||
".. gh-issue: 123456\n.. section: Funky Kong\nHello world!", | ||
r"Invalid section 'Funky Kong'! You must use one of the predefined sections", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you trying to get us sued by Nintendo?!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Funky Kong already lives here :D
https://github.com/python/blurb/blob/main/tests/fail/invalid-section.rst?plain=1
Fixes #34.
For the first part:
We were checking gh-issue is in the correct range (32426 or higher) before checking it's an int, and so getting a general
ValueError: invalid literal for int() with base 10: ''
instead of a better Blurb one:Invalid GitHub issue number! ('')
.For the second part:
Ensure one of
gh-issue
orbpo
exists in the metadata.Also add more unit tests for
Blurb.parse()
.