This is still not set in stone and not fully consistent from one
subcomponent to another, but the general idea is that instead of
passing everything in one property via v-model we use v-bind
instead with a variable list of props depending on the needs of
the subcomponent.
We listen for @input and a new @merge event in order to apply
any changes to the *local* configuration. The local configuration
then needs to be uploaded to the server via a separate step. We
might change this in a later commit, so that changes made in
subcomponents are automatically applied to the local configuration.
In short:
POST creates a new project
PUT overwrites a project configuration with a new one
PATCH merges the request body with the existing configuration
This commit adds <dougal-field-content/> and
<dougal-field-content-dialog/>, which can be
used to configure certain properties of an
object. Intended for use while editing project
configurations.
The functions are:
- deepMerge() Merge two objects
- deepCompare() Loose deep comparison
- deepEqual() Strict deep comparison
- deepSet() Set nested object property value
- deepValue() Retrive nested object property value
This is currently disabled though (value in route/index.js is
commented out) as it is not possible at the moment to create
new projects fully from scratch from the frontend. See comment
on previous commit.
NB: projects may be created fully from scratch by making an API
request with a suitable YAML / JSON configuration file, thusly:
curl -vs "https://[hostname]/api/project" -X POST \
-H "Content-Type: application/yaml"
--data-binary @/path/to/configuration.yaml
This is not usable at the moment as the backend requires even
more details, such as binning parameters, which this dialogue
does not provide.
It might be a matter of relaxing the rules on the backend or,
perhaps more likely, rethinking the project creation / editing
frontend. Maybe refactoring the frontend so that saves are done
in one go for the whole configuration as opposed to piecemeal as
currently done might make it easier to work on a configuration
(especially a new one) fully offline.
Until now, credentials were set indirectly by reading the browser's
cookie store. This change allows us to receive credentials via other
mechanisms, notably WebSockets.
