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

Split core library from high-level utilities #35

Open
gmethvin opened this issue Feb 8, 2017 · 1 comment
Open

Split core library from high-level utilities #35

gmethvin opened this issue Feb 8, 2017 · 1 comment

Comments

@gmethvin
Copy link
Member

gmethvin commented Feb 8, 2017

Libraries like Play Framework usually only need to depend on the low-level library for reading and writing JSON: JsValue, Json.fromJson/Json.stringify, etc. Many of the newer changes in play-json relate to high-level functionality like the macros and configuration that would typically only be used by the end user.

It may be useful to separate this "core" library from the more high-level parts of the library like the macros and functional transformers. This way we can add features and make binary incompatible changes to the macros (for example) without creating compatibility issues with libraries like Play.

@cchantep
Copy link
Member

cchantep commented Feb 8, 2017

The JsonFacade trait (see #34 ) can be a good start point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants