Define simple models for job messages. #19688
Draft
+184
−70
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.
Implements #19676 - first step toward proper typing on the frontend and solving one more vue-tsc error.
A note about a refactoring and dependencies
I moved the Job schema definition into the API package so it can depend on galaxy-tool-util. For now - us defining models in both galaxy-schema and galaxy-tool-util will mean combined models need to be placed in a package that depends on them both. I think longer term we will need to separate all the galaxy-tool-util models out into their own package and have galaxy-schema depend on that. Maybe I'm wrong though and the right approach is just to place all the models into galaxy-schema and update galaxy-tool-util to depend on that - I just really want galaxy-tool-util to have minimal dependencies and it seems like there is so much unrelated to artifact parsing and execution in galaxy-schema.
How to test the changes?
(Select all options that apply)
License