Json xml

[KamyaPA]

Closes #15

Changes/Additions:

• Deserialization an serialization from json of each sample type
• Moved everything into own file
• Added jsdoc documentation

[AlbertHald]

LGTM

[atjn]

I didn't have a chance to review this before it was merged, but I would have liked to see better comments. Many of them are stating something you can already read, like this one:

Some of them are adding more information, but I would argue that that information should have been in the variable names. For example, this should probably have been called a NailProperty:

The style guide that you are using also has a section for this: https://google.github.io/styleguide/tsguide.html#redundant-comments

A better comment would say "this property is being used by fn1 and fn2 to do this", or "this function is using these and these features to solve this problem". Design considerations and gotcha's are also welcome. "we made this property to solve x problem, be aware that if you want to do y, there is an issue with this".

If you don't know what they are being used for, or don't know what to write that could be helpful, it is better to add a comment with a TODO: Document the use of this prop, because this makes us able to search the codebase for "TODO" and fix things later when we have more knowledge.

[atjn]

@KamyaPA I don't know if this is something that you want to work on yourself? I can also add an issue, and we can put it into our sprint at some point :)

[atjn]

Btw, it is hard to search for ? because there will be a thousand lines of code that is using the questionmark legitimately. It is much better to use TODO, as that will only be present in places where there is work to be done.