-
Notifications
You must be signed in to change notification settings - Fork 283
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
Modified artio frontend fields to ytep 0003 conv: Issue/2608/artio #2613
Modified artio frontend fields to ytep 0003 conv: Issue/2608/artio #2613
Conversation
Hi! Welcome, and thanks for opening this pull request. We have some guidelines for new pull requests, and soon you'll hear back about the results of our tests and continuous integration checks. Thank you for your contribution! |
Thanks you for opening this !
Disclaimer: I am unfamiliar with the way we maintain support to unconventional (violating YTEP-0003) field names. After careful examination my take on this is that the code in I would like to request a second opinion from someone more experienced. @brittonsmith, since you were the one to mention the violation of YTEP-0003 originally, could you give any feedback ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for doing this!
@neutrinoceros -@cavestruz and I are considering opening a new issue for the deprecated fields warning, unless someone else wanted to do that. Also @brittonsmith and @matthewturk: can both this PR and PR #2604 be a squashed and merged to master so I can do analysis from the master branch? |
Sorry for taking so long to weigh in on this. The fields in I'm in favor of merging this and creating an issue to remind ourselves that the new fields added to @neutrinoceros, I will approve this and if you agree, you can be the third approval and merge this. |
Let's also merge PR #2604 as well and maybe someone can follow up with a quick PR to add the correct field alias for |
not sure I understand what remains to be done actually. I'm okay to merge this however ! |
Hooray! Congratulations on your first merged pull request! We hope we keep seeing you around! 🎆 |
PR Summary
Modified ARTIO variable names to YTEP-0003 conventions for Issue #2608
Question: @Provider10 and I would like to make sure that folks using the other field names can easily use (and know to use) the back-compatibility functionality. We are open to any thoughts or suggestions for putting in a specific error message for ARTIO users to let them know that they are missing the if the ds._setup_deprecated_fields() if the user has not added it, which we can add before this PR is merged.
Addresses: Issue #2608
PR Checklist