-
Notifications
You must be signed in to change notification settings - Fork 1
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
Wildcard versioning not working correctly #44
Comments
@DennisReddyhoff Any details on this? i.e. inputs etc |
@kzscisoft I understand that when you run a user config with a wildcard in the |
So you are saying that the version variables are working but just not for wildcard statements? This could be an ordering thing, maybe I put the wildcard parsing after the version parsing when it should come before. The versioning should be working for most cases |
Hmm it should be working, I could do with a failing example |
Okay. Here you go... I've put three files in Zulip as I can't upload them here. First register.yaml then write.yaml produces config.yaml. This is just Sonia's basic registration example: (fair-6UDMIGpx-py3.8) (base) bleaberry[~/Documents/git/julia/EcoSISTEM] fair pull register.yaml
Updating registry from config.yaml
(fair-6UDMIGpx-py3.8) (base) bleaberry[~/Documents/git/julia/EcoSISTEM] fair pull write.yaml
Updating registry from config.yaml
(fair-6UDMIGpx-py3.8) (base) bleaberry[~/Documents/git/julia/EcoSISTEM] fair run write.yaml
Updating registry from config.yaml
Hello World!
write:
- data_product: records/SARS-CoV-2/scotland/*
file_type: csv
use:
version: 0.20210901.1
- data_product: records/SARS-CoV-2/scotland/human-mortality
file_type: csv
use:
version: 0.20210901.1 This is the right version for |
Closed in #57. |
When using wildcards, the version is not correctly returning as '0.0.1'
The text was updated successfully, but these errors were encountered: