Repository navigation
Add static analysis script for aio source code consistency - #116
Merged
Merged
Conversation
Contributor
|
General Question: When is this intended to be run? I think it should be run when changes are made to any handwritten packages and in our release infrastructure. Is that what you had in mind? Edit: Or maybe just handwritten packages here if smithy is already enforcing it for generated clients? |
Contributor
Author
|
it's fast, so it should be early on in the CI process. |
ubaskota
approved these changes
Oct 29, 2026
stobrien89
approved these changes
Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Same as smithy-lang/smithy-python#875
adds an aio linting script to be part of CI in the future, once existing failures are repaired.