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

chore: add comments to exports in user impl module #4

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

nilslice
Copy link
Member

@nilslice nilslice commented Sep 3, 2024

Partially completes #2

After looking at it more, I think the paths are way simpler to leave in the types, and not that hard for the end-user to remove & add a use themselves. There's a few different contexts in which this bindgen would need to check if a use statement is needed, and it's a bit complex to abstract, and alternatively super verbose to check around all the edges.

@@ -97,7 +97,7 @@ export function render() {
makePublic,
jsonWrappedRustType,
capitalize,
camelToSnakeCase
camelToSnakeCase,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just editor formatting

Copy link
Contributor

@zshipko zshipko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! I agree that leaving the full path to types is fine for now - in the case of serde_json::Value it might be more helpful to know Value type is coming from serde_json without having to check (although checking isn't so hard either)

@nilslice nilslice merged commit cd6ace1 into main Sep 3, 2024
1 check passed
@nilslice nilslice deleted the more-comments branch September 3, 2024 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants