Another refactoring. What we're doing now is eliminating the
need to save individually on each section. Configuration changes
are done directly on the local configuration and then the local
configuration is saved, downloaded or discarded in one go.
This script rewrites project configurations to take into account
various structural changes in the configuration object.
The script can be run without arguments, in which case it will
upgrade the configuration of every project found in the local
database, or one or more project IDs can be given as command
line arguments in order to upgrade only those projects.
Configurations that have already been upgraded will not be
touched.
For other projects, both the original and new configurations will
be saved to file in the current directory, as well as two scripts:
one commits the new configuration to the server, and the other
restores the original one.
This script connects directly to the database, using the same
mechanisms as the Dougal server. It is recommended to run it
locally on the server host.
The restore scripts use the HTTP API, which they expect to find
on http://localhost:3000/api, so it is also recommended to run
them in the local server.
Closes#290.
Closes#291.
Closes#292.
Closes#293.
Closes#294.
Closes#295.
Closes#296.
Closes#297.
Closes#298.
This view shows a tree view of the raw JSON configuration
object, allowing the user to add / edit / delete any properties
whatsoever. It is semi-hidden behind a context menu. The user
has to right-click on the header of the left-hand column showing
the list of configuration sections and then click on the red
"advanced configuration" button. In the advanced configuration
view there is another button to go back to normal configuration.
It is only possible to save / refresh the configuration from the
normal view.
- Use a fixed width name parser rather than regular expressions
- Move the Smartsource header files configuration to a different
part of the configuration object.
- Uses the new interface with the main component
- Changes the path where ASAQC related settings are saved,
from $.asaqc to $.cloud.asaqc.
- Adds field for configuring the subscription key.
This introduces a number of changes, most notably an easier way
to specify fixed width formats and support for configuring
multiple import options (actual SPSv1, SPSv2.1, P1/90, CSV, …)
Note that only the configuration GUI is done, support for actually
importing those formats has not been implemented as of this commit.
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
