-
Notifications
You must be signed in to change notification settings - Fork 5
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
Replace usage of ioda v1 naming with ioda v2 naming #1286
Comments
@srherbener sigh, think we've done most of this but should see if we don't have a technical debt label |
@srherbener is this done? or work yet to be scoped? should it be closed |
I'm still seeing a lot of usage of the v1 syntax:
On one hand it would be nice to eradicate the usage of the v1 syntax, but on the other we can handle it and I think it might not be worth the effort since there is still a lot of places I found the usage. I trimmed down the listing above for posting in this issue - deleted something like 1300 lines. Perhaps we could write a script to help but I think we should consider whether it's worth the effort. |
@srherbener The BUFR related YAML files need to be removed anyways, so wouldn't bother with them. See #1586. |
Description
We need to go through all of the YAML configuration files and code, and replace the "variable@group" (ioda v1 naming) specifications with "group/variable" (ioda v2 naming).
Some examples where the ioda v1 naming is used:
Mike Cooke from the Met Office supplied a script that may be helpful with this task. See https://github.com/JCSDA-internal/ioda/issues/379#issuecomment-1614810874 for more information.
Requirements
All YAML files and code need to get updated to ioda v2 syntax so that eventually we can deprecate the ioda v1 syntax.
Acceptance Criteria (Definition of Done)
All instances of "variable@group" have been replaced with "group/variable".
All ctests pass
Dependencies
None.
The text was updated successfully, but these errors were encountered: