kinokabaret/axiom-webremote

Vue-ified webgui with development server, ES6 linting and tests

axiom-webremote's Issues

Validate localstorage values against a registry.

On load we'll need to instruct the code to look at the registry and make sure that we have sensible ID's and VALUE's before we try to add them anywhere - or worse - post something nasty to the camera's server.

This also needs to be done server-side - but that is out of scope here.

Mutation Translation / Alert Hook

It seems that we don't have access to either the i18n scope or Quasar from within the mutations.js provider. Some kind of hook will be required to call the Mutator so that we can have feedback on the screen as a chromed alert, instead of just in console.log(). Although not "necessary", I prefer to translate everything from strings instead of hardwiring content into anything. This is why the API replies with a translation primitive instead of a "real response".

We have access to this stuff in common.js - so that's probably where to put it.

start command finetuning

it should be:

$ cd dist/spa-mat && python -m SimpleHTTPServer

Endpoint Construction

I suggest that we define an API spec call where the SERVER provides a list of calls that it will accept - a kind of self-documenting spec.

This way, instead of hardwiring everything into the front-end, we expect that the SERVER tells us what it is currently capable of. This should be in JSON and include Translations for the interface. Once it arrives, we inject it into the front-end and alert the SERVER that the interface is ready to start C&C.

I imagine something like this:
<service.ip>:<service.port>/api/<api.version>/dictionary to give us:

https://192.168.1.1:7070/api/v1/dictionary

And the last line is: dictionary.slice(-1)[0] // to get the last element in the array