-
Notifications
You must be signed in to change notification settings - Fork 37
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
Rename NamingStrategy to FieldNamingStrategy #178
Labels
enhancement
New feature or request
Milestone
Comments
Chuckame
added a commit
to Chuckame/avro4k
that referenced
this issue
Jan 28, 2024
…pace] and add AvroNamespaceOverride (avro-kotlin#165)
Chuckame
added a commit
to Chuckame/avro4k
that referenced
this issue
Jan 28, 2024
…pace] and add AvroNamespaceOverride (avro-kotlin#165)
Chuckame
added a commit
to Chuckame/avro4k
that referenced
this issue
Feb 3, 2024
…pace] and add AvroNamespaceOverride (avro-kotlin#165)
Chuckame
added a commit
to Chuckame/avro4k
that referenced
this issue
Apr 10, 2024
…pace] and add AvroNamespaceOverride (avro-kotlin#165)
Done in #182 |
Chuckame
changed the title
Split NamingStrategy to specific record and field strategies
Rename NamingStrategy to FieldNamingStrategy
May 23, 2024
open it back, waiting for a real release |
Released in v2.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current issue
Now, defining a naming strategy impacts both records' and fields' name... Well it seems. It only applies the naming strategy to field names (and the fixed names as it relies on the field name).
Proposal
Have a clear
FieldNamingStrategy
and improve the interface:The text was updated successfully, but these errors were encountered: