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 generic impl #281

Merged
merged 4 commits into from
Mar 22, 2024
Merged

Conversation

aumetra
Copy link
Contributor

@aumetra aumetra commented Mar 22, 2024

Goal

When deriving ts_rs::TS for a struct with a generic type parameter, the code expanded to requiring the ts_rs::TS trait to be in scope.
This should be fixed.

Changes

This PR fixes this by using the newly introduced crate_rename path, interpolating the path to be #crate_rename::TS

Checklist

  • I have followed the steps listed in the Contributing guide.
  • If necessary, I have added documentation related to the changes made.
  • I have added or updated the tests related to the changes made.

Copy link
Contributor

@escritorio-gustavo escritorio-gustavo left a comment

Choose a reason for hiding this comment

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

LGTM! @NyxCode, I think we should make a 8.1.0 release after merging this PR. What do you think?

@escritorio-gustavo escritorio-gustavo merged commit 88c2ae8 into Aleph-Alpha:main Mar 22, 2024
7 checks passed
@aumetra aumetra deleted the fix-generic-impl branch March 22, 2024 12:47
@NyxCode
Copy link
Collaborator

NyxCode commented Mar 22, 2024

whoops, guess we missed that.

I think we should make a 8.1.0 release after merging this PR. What do you think?

I'd be open to. Let me first take a look at #282 and #280, to see if we can include them as well.

@NyxCode
Copy link
Collaborator

NyxCode commented Mar 22, 2024

@escritorio-gustavo I think #280 needs a bit more time, right? Should I publish a 8.1.0 from the current master as-is?

@escritorio-gustavo
Copy link
Contributor

@escritorio-gustavo I think #280 needs a bit more time, right? Should I publish a 8.1.0 from the current master as-is?

Agreed, I'd love to have that fully functioning before it gets to a release

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

3 participants