Skip to content

Fix JsonB generic generation errors #543

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

Merged
merged 5 commits into from
Jan 12, 2025
Merged

Conversation

SentryMan
Copy link
Collaborator

@SentryMan SentryMan commented Jan 12, 2025

  • add a method to UType to retrieve the parameters
  • add debug toString to appender

Resolves #542

@SentryMan SentryMan added the bug Something isn't working label Jan 12, 2025
@SentryMan SentryMan self-assigned this Jan 12, 2025
@SentryMan SentryMan enabled auto-merge January 12, 2025 02:12
@SentryMan SentryMan requested a review from rbygrave January 12, 2025 02:12
@SentryMan SentryMan disabled auto-merge January 12, 2025 02:12
@SentryMan SentryMan enabled auto-merge (squash) January 12, 2025 02:12
@SentryMan SentryMan merged commit 34257d6 into avaje:master Jan 12, 2025
6 checks passed
@rbygrave rbygrave added this to the 3.0 milestone Jan 12, 2025
@SentryMan SentryMan deleted the genericIssue branch January 12, 2025 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Generated avaje-jsonb code does not work when using generic return types
2 participants