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

fix(provider-wit-bindgen): argument bundling & type resolution #1587

Conversation

vados-cosmonic
Copy link
Contributor

Feature or Problem

This commit fixes two issues with provider bindgen:

  • Types replaced as part of structs were using their full qualified paths, depsite types being lifted to the top level (with structs), not needing it.

  • Invocation arguments for LatticeMethods that were recorded were not being saved when processing structs. This comes up when exporting a function that needed it's arguments bundled into a struct

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

This commit fixes two issues with provider bindgen:

- Types replaced as part of structs were using their full qualified
paths, depsite types being lifted to the top level (with structs), not
needing it.

- Invocation arguments for `LatticeMethod`s that were recorded were
not being saved when processing structs. This comes up when exporting
a function that needed it's arguments bundled into a struct

Signed-off-by: Victor Adossi <vadossi@cosmonic.com>
@vados-cosmonic vados-cosmonic requested a review from a team as a code owner February 27, 2024 12:33
Copy link
Contributor

@ricochet ricochet left a comment

Choose a reason for hiding this comment

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

I wish there was a test to see the difference in output but I understand how that is likely difficult to add right now.

@vados-cosmonic vados-cosmonic merged commit 27075f1 into wasmCloud:main Feb 27, 2024
43 checks passed
@vados-cosmonic vados-cosmonic deleted the fix(provider-wit-bindgen)=misimported-type branch February 27, 2024 15:02
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.

None yet

2 participants