#Json #Reads/#Writes for a sealed #trait & inheriting caseclasses without type indication in Json #Play2.1

README.md

Xamplez's Root Gist of the Root Gists

Instructions for Xamplez administrators

When you create a new instance of Xamplez, you must first fork your configuration from the Lord of the Gists. Then, you create your Root Gist(s) by forking this Root Gist of the Root Gists. It just gives a default template that you can modify. Finally, make the configuration gist point to this/these Root Gist.

Instructions for Xamplez code snippet creators

How to use

1. Fork the Root Gist to create a new snippet.
2. Modify your gist according to Rules.
3. Save it and wait for to index it.

Rules

1. You MUST put a gist description which summarizes your snippet as precisely as possible.
2. All words starting in the description with a dash #tag are indexed as tags.
3. You can add as many files as you want in your gist
4. File extensions are used to identify the language (e.g. code.scala -> scala)
5. A code snippet shouldn't be too big (a few lines if possible) so don't hesitate to cut in several files
6. If you want to explain precisely your code or provide usage examples, please use a Markdown file (e.g. README.md)
7. You can put a License in case your code need to be protected in anyway

_LICENSE.txt

            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
                    Version 2, December 2004

 Copyright (C) 2013 YOUR_NAME_HERE <YOUR_URL_HERE>

 Everyone is permitted to copy and distribute verbatim or modified
 copies of this license document, and changing it is allowed as long
 as the name is changed.

            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. You just DO WHAT THE FUCK YOU WANT TO.

CODE

<put your code here>

Thanks man!