Add deprecation warnings for all variable hierarchy name changes since 1.0.
Open
Nobody has claimed this yet.
documentation
request
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Description
Name changes can catch people by surprise. We should enforce some kind of warning behavior to help them migrate their csv file or components to address the changes.
There are different ways we can handle this:
- raise an error?
- raise a warning and automatically replace the old names with the correct ones?
- do we keep the old names in the hiearchy?
- how long until we remove the deprecation?
Example
No response
Error Message
No response
Aviary Version
1.0.3-dev
Environment Information
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.