-
Notifications
You must be signed in to change notification settings - Fork 5
Improve execution #109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Improve execution #109
Conversation
This file contains hidden or 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
otherwise page link from the execution page to the component details will land on the component list page
add validator for step number to be an integer below a threshold add validator for a port mapping
display also same components as different steps in the workflow initialize mermaid diagram since this is necessary even if it does not carry any items add new functions to get keys and values form parameters add custom dashboard function for display of component versions
use user workdirectory instead of home directory as base when picking the project path
the form for creating executions was completely refactored: it is now able to have executions that have multiple steps that are based on the same component version. Parameters can be loaded into the form from files and then overwritten. The form recognizes its state and the user can walk between steps with ease without losing any previous inputs in the execution table the order of the executions changed: the newest executions come first now
this setting is needed in the dasboard to set a users base directory
allow users to set a working directory that will be used as base when reading files from the server
this will be used as starting point for users to set their working directory on the dashboard
add two new function to get a collection back sorted by field field values extend existing function with an option to sort and the default for this new argument is None the new fuctions will be used to sort component versions and executions
the new setting variable is not needed
adapt github repo validator to include more cases: this validator returns errors and is used differently than other validators as it should not run too often, just once after the user has finished his input field entry a new validator is added to check whether a path is already taken
in most cases this can be better done in the page code files only where a write function is shared it is kept in the storage helper
sort versions by components and tags improve validation of component url when adding a new component
sort versions by components and then tags in the workflow selection improve storage handling
also add a button to create a new project directory
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.
No description provided.