It's similar to <dougal-fixed-string-decoder-field/> but it handles
static strings.
Used to match, e.g., file names, where certain parts of the name
are expected to contain a specific string (such as a project prefix
and the like).
This supports CSV and similar formats, as well as sailline
imports, which is a CSV file with a specific set of column
definitions.
Does not yet support P111 import (for which there is an
implementation already).
This supports reading: SPSv1, SPSv2.1, P190 and custom
fixed-width formats. Supports skipping lines by startswith()
matching or by complete match (e.g., "EOF").
Closes#300 (SPS v1)
Closes#301 (SPS v2.1)
Closes#302 (P1/90)
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.
