Topping on create Project #858
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… we provide it to the gui. we can disable the metaconfig from the database and select another project topping from the usabilityhub or from the local system. when a topping is selected we disable the optimize strategy.
|
Any inputs on that @geckoGIS ? |
domi4484
approved these changes
Dec 4, 2023
That's pure magic 🧙 It's the |
Co-authored-by: Damiano Lombardi <[email protected]>
domi4484
approved these changes
Dec 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Topping on Generate
Get Topping of Metaconfig stored in the DB
Since ili2db 4.11 the id of the metaconfiguration file used to create the physical database is stored in the meta-tables. This means, on Project Creation we consider this id and provide the linked project topping.
Get Topping by selection
Still it's possible to disable it and choose another project topping file.
You can choose a project topping file (identified by model, db-type) from the UsabILITy Hub repositories or as well a YAML file from the local system.
Why, project topping file
... and not "metaconfiguration* file?
Because on this step only project topping files are relevant. Metaconfiguration files are only relevant, when the schema is created. We thought about to provide them, to choose the same like on schema import, but this part is already provided by getting the topping from the DB.
To do
Resolves #479 and resolves #768
Busy Bar
Not directly related to this topic but it popped up again. Sometimes the wizard has to load - mostly checking the repos to suggest data / reload the comboboxes. And there users are confused, what's happening. For this reason it does now:
Screencast.from.04.12.2023.16.24.24.webm