Skip to content
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

x/mobile: output diagnostic messages when skipping variables and methods #41937

Open
federicobond opened this issue Oct 12, 2020 · 1 comment · May be fixed by golang/mobile#54
Open

x/mobile: output diagnostic messages when skipping variables and methods #41937

federicobond opened this issue Oct 12, 2020 · 1 comment · May be fixed by golang/mobile#54
Labels
FeatureRequest mobile Android, iOS, and x/mobile NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@federicobond
Copy link

The current version of the gomobile/gobind tool silently skips methods and variables that are not supported by the bridge. The only indication that this has happened is found in the comments of the resulting bridge source files.

It would be very useful for the tool to also emit diagnostic messages to the console including the location of the objects that were skipped. This could be further extended with a mechanism to return a failure error code in the command if any objects were skipped, and some way to ignore these warnings for specific objects.

@gopherbot gopherbot added the mobile Android, iOS, and x/mobile label Oct 12, 2020
@gopherbot gopherbot added this to the Unreleased milestone Oct 12, 2020
@dmitshur dmitshur added FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Oct 13, 2020
@dmitshur
Copy link
Contributor

CC @hyangah, @hajimehoshi.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FeatureRequest mobile Android, iOS, and x/mobile NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants