-
Notifications
You must be signed in to change notification settings - Fork 65
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 all schemas defined in the spec as valid JSON schemas #294
Conversation
API specs implemented for 307/649 (47%) APIs. |
Converting this to draft because I've just discovered that I can turn strict mode on and it's catching a lot more infractions in our current spec. Look into that now |
API specs implemented for 307/649 (47%) APIs. |
5 similar comments
API specs implemented for 307/649 (47%) APIs. |
API specs implemented for 307/649 (47%) APIs. |
API specs implemented for 307/649 (47%) APIs. |
API specs implemented for 307/649 (47%) APIs. |
API specs implemented for 307/649 (47%) APIs. |
@dblock These comments are getting out of hand 😅 There should be a cool down period, or maybe it should only be triggered when the PR is first created and/or ONLY run it constantly like this when a certain tag is attached to the PR? |
For sure. It could delete the previous comment/update the existing one, etc. Feel free to open an issue. |
API specs implemented for 307/649 (47%) APIs. |
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.
It's not a lot of changes, but you might want to split up logger changes.
API specs implemented for 307/649 (47%) APIs. |
1 similar comment
API specs implemented for 307/649 (47%) APIs. |
API specs implemented for 307/649 (47%) APIs. |
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.
Write tests for logger, flip order. Sorry to be annoying ;) Otherwise this PR LGTM.
tools/src/Logger.ts
Outdated
export enum LogLevel { | ||
info = 1, | ||
warn = 2, | ||
error = 3 |
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.
In all the loggers the order is usually the other way around, you should flip these.
https://stackoverflow.com/questions/2031163/when-to-use-the-different-log-levels
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.
Ahhh Today I learned. Thanks
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.
It's been updated now. I've squashed all commits too. Feel free to merge it after approving.
- Updated default arg values for merge.ts - Added Logger to silence merger tool's warnings - Added SchemasValidator Signed-off-by: Theo Truong <theotr@amazon.com>
fb4329c
to
747be0a
Compare
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.