Redo Mirage config from from scratch about ontohub-frontend

[eugenk]

I like the idea of generating the models (non-frontend-specific things) directly from the JSON Schema in the backend and I have given https://github.com/thoughtbot/ember-json-schema a try, but it does not work out of the box with our JSON Schema definitions.

It does not use the attributes and relationships keys from the schema and only relies on the properties key, which is not defining a single property of the object (except for id and type which should be ignored anyway).

I think we should follow its idea to reduce work in the long run. Then, we would not need to duplicate our models in the frontend and the backend. We could fork the project and make it work with proper JSON Schema.

[eugenk]

With my fork at https://github.com/eugenk/ember-json-schema, this works. We need some conventions, though, concerning the JSON Schema files. They are be compiled in ontohub/ontohub-backend#71.

And we still need to resolve $ref in the JSON Schema.

[eugenk]

Instructions to try this:

1. backend: git checkout 71-structure_json_schema_files
2. backend: rails s
3. frontend: git checkout 41-redo_mirage_config_from_from_scratch
4. frontend: ln -s <ontohub-backend-repo>/spec/support/api/schemas app/schema (in the repository-root)
5. frontend: ember s
6. http://localhost:4200/ada/repo0

[eugenk]

I added a commit to the ember-plugin's repo that should resolve $refs, but it doesn't work because it tries to resolve them relative to the address (e.g. http://localhost:7357/2173/tests/other.json instead of the local path ./other). I don't have an idea of how to do this.

Edit: Before, I said that I added a commit to the frontend branch. This was wrong...

[phyrog]

Closed in #62.