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

Correctly record Optionals containing custom classes #8745

Merged
merged 1 commit into from
Apr 23, 2020

Conversation

jmartisk
Copy link
Contributor

Fixes #8744

@gsmet
Copy link
Member

gsmet commented Apr 22, 2020

@jmartisk is it something we want in 1.4 or it's only useful for future developments?

@jmartisk
Copy link
Contributor Author

@gsmet This is a bug affecting extension developers, we found it while coding the GraphQL extension, but managed to work around it, so I think it's not that critical. But it could potentially affect other extensions, so I'd vote for including it.

@gastaldi gastaldi added this to the 1.5.0 milestone Apr 22, 2020
Copy link
Contributor

@gastaldi gastaldi left a comment

Choose a reason for hiding this comment

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

LGTM

@gsmet
Copy link
Member

gsmet commented Apr 22, 2020

@stuartwdouglas I let you check that one and merge?

@stuartwdouglas stuartwdouglas merged commit 332b43d into quarkusio:master Apr 23, 2020
@jmartisk jmartisk deleted the master-issue-8744 branch April 23, 2020 05:11
@gsmet gsmet modified the milestones: 1.5.0, 1.4.0.Final Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Recording broken for Optionals containing custom classes
4 participants