fix(lint): use buf plugins for lint and fixes for AEP compliance. #28
Conversation
This file contains 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
toumorokoshi
force-pushed
the
yft/buf
branch
2 times, most recently
from
b2f2b6a to
227827c
Compare
toumorokoshi
force-pushed
the
yft/buf
branch
3 times, most recently
from
784e12f to
985e917
Compare
Using buf plugins for linting is a more ergonomic approach, avoiding the need to manually clone googleapis. Fixes to reach AEP compliance: - removing apply method as it is not an official AEP at the moment.
toumorokoshi
force-pushed
the
yft/buf
branch
from
985e917 to
1147656
Compare
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.
Using buf plugins for linting is a more ergonomic approach, avoiding the need to manually clone googleapis.
api-linter was updated with fixes, so this change was just switching to buf lint and adding it to github actions: aep-dev/api-linter#93.