-
Notifications
You must be signed in to change notification settings - Fork 3
feat(api-history): --check-descriptions
#80
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
Conversation
--check-descriptions
dsanders11
left a comment
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.
This looks good minus one comment about a continue statement.
Worth noting that this only allows for single-line quoted descriptions. In theory the user could provide a multi-line quoted description, but I think it's fine to only support single-line for now.
Co-authored-by: David Sanders <dsanders11@ucsbalum.com> Reference: #80 (comment)
https://stackoverflow.com/a/21699210
I think I might leave that for someone else to figure out 😭 |
* feat(api-history): `--check-descriptions` Reference: #78 (comment) * test(api-history): description test * fix(api-history): only double quotes * feat(api-history): `--disallow-comments` Reference: #79 * feat(api-history): traverse tree instead * fix(api-history): description `for` loop Co-authored-by: David Sanders <dsanders11@ucsbalum.com> Reference: #80 (comment) * style(api-history): fix lint, leave comment --------- Co-authored-by: David Sanders <dsanders11@ucsbalum.com>
|
🎉 This PR is included in version 2.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Resolves: #78
Throws error if description field is not surrounded by double quotation marks.
@dsanders11 @erickzhao @VerteDinde