Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Missing machinery for frontend-specific deprecated field names #2649

Closed
neutrinoceros opened this issue Jun 19, 2020 · 2 comments
Closed

Missing machinery for frontend-specific deprecated field names #2649

neutrinoceros opened this issue Jun 19, 2020 · 2 comments
Labels
new feature Something fun and new! wishlist Things we'd like to do some day

Comments

@neutrinoceros
Copy link
Member

Report

In the discussion around #2613, @brittonsmith proposed that we add a mechanism to attach deprecated field names to specific frontends. Currently all deprecated field names are stored in yt/fields/field_aliases.py.

It seems likely to me that all field names collected in this file are in fact meant to support a specific frontend, and maybe it they can be traced back with git blame.
@neutrinoceros neutrinoceros added wishlist Things we'd like to do some day new feature Something fun and new! labels Jun 19, 2020
@munkm
Copy link
Member

munkm commented Jun 19, 2020

I'm confused, why were there three issues all with this name?

@neutrinoceros
Copy link
Member Author

Because I submitted this while on a train and went into network issues.

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
new feature Something fun and new! wishlist Things we'd like to do some day
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@munkm @neutrinoceros