-
Notifications
You must be signed in to change notification settings - Fork 334
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
Support for various JSON libraries #846
Comments
@magnolia-k Great! I will check your code as soon as possible. |
I think it's impossible to make with the current Scalatra API because it allows any types as the result of the action. Dramatic changes in core API is necessary. My idea is defining a type class like
spray-json and argonaut is good start of the multiple JSON library support in Scalatra! |
thank you for your comment There seems to be a need to think towards the function of Scalatra 3.0 (?). First of all, prepare for Scalatra 2.7 with case class support removed. |
Make sense.
What does it mean? |
If we put Spray-Json and Argonaut's support in 2.7, we mean we have to decide whether or not to add without support for case class It does not mean to remove case class support from json4s. |
I totally understood. While that's nice as a first step of multiple JSON library support, I would like to consider introducing the type class to render response. But I'm not sure whther it's possible to introduce it in Scalatra 2.7 at the moment. We will able to consider case class support in JSON support after that. |
I wrote a prototype of support for Spray-Json and Argonaut
Spray-JSON
magnolia-k@46d8a5c
Argonaut
magnolia-k@caad122
Things to decide to support various JSON libraries
The text was updated successfully, but these errors were encountered: