-
Notifications
You must be signed in to change notification settings - Fork 144
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
aip-133: request-parent-required fires for a top-level resource #599
Comments
This is a linter bug, yeah. |
Actually, we have code for this and a test for this. Are you using a current version? Closing now, but feel free to reopen if appropriate. |
I'm using |
What does |
|
lukesneeringer
pushed a commit
that referenced
this issue
Sep 2, 2020
Also, I rewrote the tests for these rules from scratch, as they were in a weird state. Fixes #599.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I see the error https://linter.aip.dev/133/request-parent-required for a top-level resource. https://google.aip.dev/133 states "A parent field must be included unless the resource being created is a top-level resource."
Is this a bug with the linter, or is there some way I should I be tagging my top level resources? To reproduce the error create a file
file.proto
with the following content:and run the api-linter to see the following problems:
The text was updated successfully, but these errors were encountered: