-
Notifications
You must be signed in to change notification settings - Fork 14
The single-field class formatter should support standard Play format #4
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
Comments
+1 |
3 similar comments
+1 |
+1 |
+1 |
👍 :) |
mslinn
pushed a commit
to mslinn/json-annotation
that referenced
this issue
Oct 6, 2019
…parsing Remove robust json parsing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We would love to use your plugin at Gravity, but unfortunately it would require a difficult migration for certain single-value case classes that use the standard Play format (e.g.
{"name":"Bob"}
forcase class Person(name: String)
). The problem is that we have many such classes and serializations being stored and transmitted among many apps; to use your plugin as-is we would have to perform a difficult migration involving hundreds of servers.Would it be possible for you to release a patch to support "backwards compatibility" with the default Play format for single-value case classes? If not, I suppose I could do my best to submit a PR with one, but chances are you'll be able to whip that out much more quickly as I have no macro experience...
The text was updated successfully, but these errors were encountered: