We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've made it hard on myself by re-using the terms suite, key several times. I propose new naming scheme for the input configuratrion yaml files:
input_yml
comparisions
key_list
suites
key_files
keys
Models
coordinate_schemes
The text was updated successfully, but these errors were encountered:
name them however you think appropriate - you da boss - just make sure it gets documented 😁
Sorry, something went wrong.
No branches or pull requests
I've made it hard on myself by re-using the terms suite, key several times. I propose new naming scheme for the input configuratrion yaml files:
input_yml
becomescomparisions
key_list
becomessuites
key_files
becomeskeys
Models
(work in progress) becomescoordinate_schemes
or similar.The text was updated successfully, but these errors were encountered: