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

Introduce @CodecProvider for discovery of user supplied CodecProviders #2232

Open
evanchooly opened this issue Jan 23, 2023 · 2 comments
Open
Labels
enhancement proposed Potential new features
Milestone

Comments

@evanchooly
Copy link
Member

evanchooly commented Jan 23, 2023

see this discussion for context.

@evanchooly evanchooly added enhancement proposed Potential new features labels Jan 23, 2023
@evanchooly evanchooly added this to the 3.0.0 milestone Jan 23, 2023
@eheimburg
Copy link
Contributor

eheimburg commented Feb 20, 2023

I've been thinking about solutions to the enum-codec bug (#2264) that doesn't impact performance. (The obvious fix is to remove the built-in enum-to-string Converter, but I'm not sure about the performance impact.)

Maybe this proposed new @CodecProvider annotation could help here too: maybe the built-in converter could first check if that annotation is present for the enum -- if it is, it can just not convert that type.

@evanchooly evanchooly modified the milestones: 3.0.0, 2.4.0 Feb 20, 2023
@evanchooly evanchooly changed the title Introduce @CodeProvider for discovery of user supplied CodecProviders Introduce @CodecProvider for discovery of user supplied CodecProviders May 16, 2023
@evanchooly
Copy link
Member Author

this will be better handled with 3.0's build-first approach

@evanchooly evanchooly modified the milestones: 2.4.0, 3.0.0 Jun 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement proposed Potential new features
Projects
None yet
Development

No branches or pull requests

2 participants