Query and QueryConfig layers

[sametcodes]

We have no view layer. Metric functions are reachable directly from the internet. For instance, even if the user doesn't enable a metric function, other users can still access the metrics functions publicly if the user has a connection on that platform. It causes a privacy issue.

One another problem with the current version is we cannot provide if the metric function requires parameters. It works custom.

The solution is to have a view layer. Views will hold the configurations and parameters provided by users; if a user provides no configuration, nothing will be publicly exposed.

Query layer

All the layers after having the View layer

[sametcodes]

• Make changes on the migration script
• Platform is not mapping to PlatformQuery on the database
• Build relations between Platform, User and Query models on the prisma schema
• Tests will be changed according to new endpoints (see Tests, tests, tests #34)
• Create an application for localhost development on stackapps (reconsidered that it's not necessary)
• Remove ts-ignores (see Make the code all typesafed #17)
• Nivo components returns SVGs in a parent div, it should be trimmed to SVG document
• The root SVG document should contain xmlns and xlmns:xlink attributes

[sametcodes]

Query, QueryConfig and Platform model relations.

[sametcodes]

How the View API works: