Constraints refactor to introduce a specific models package #68
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.
Hi @jagedn 👋
While testing the #66 PR, I realized that we are using the
Spec
names quite often within the main source code, however as per Groovy best practices, maybe we should reserve that name only fortests
.With that in mind, I have refactored your PR to introduce a
nextflow.nomad.models
to accommodate all the utility classes which we need to model the configuration layer for the plugin.Please let me know what do you think about the new structure overall?