Deprecate legacy `include` in model classes
Open
- Dominant language
- Python
- Stars
- 124
- Forks
- 24
- Avg merge
- 19h 32m
- Merged PRs (30d)
- 60
Description
> @AlexanderFengler `include` is a legacy naming convention from HDDM. However, to me it's kind of confusing now. Should we deprecate this for something clearer? We can use an alias for now with a deprecation warning and completely remove it in a future release
_Originally posted by @digicosmos86 in [#915](https://github.com/lnccbrown/HSSM/pull/915/changes#r2883999370)_
Contributor guide
Research direction
No file or test is named in the issue. Search the model classes and their usages for the legacy `include` name, then determine the clearer replacement intended by the project discussion. Done means the legacy name remains available through an alias with a deprecation warning, with coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100