You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[pigeon] make sure the generated code is free of analyzer warnings #59116
There are probably still analyzer warnings. There has been some steps that make this not as big of a deal. Internally the code is generated, not checked in and we've added "generated" annotations which causes them to be treated different.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
[-][[/-][+][pigeon] make sure the generated code is free of analyzer warnings[/+]xster commentedon Apr 15, 2021
@GaryQian can you check this out too? It might already be solved though since Aaron added linter checks to the tests for Java.
GaryQian commentedon Aug 9, 2022
@gaaclarke Is this still a problem with Pigeon?
gaaclarke commentedon Aug 9, 2022
There are probably still analyzer warnings. There has been some steps that make this not as big of a deal. Internally the code is generated, not checked in and we've added "generated" annotations which causes them to be treated different.
stuartmorgan-g commentedon Jan 4, 2023
We should turn on warnings-as-errors in the integration test host plugin for all languages, which would cover most of this.
[pigeon] Fix Object arguments in Swift and C++ (#3020)
github-actions commentedon Mar 14, 2023
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.