OpenAssetIO / OpenAssetIO/OpenAssetIO-TraitGen
Specification "inheritance"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
What
Determine if/what a mechanism would look like that helps people create new specifications that extend existing ones.
For example, extending an ImageSpecification with another trait to make a TextureSpecification
Why
Presently, you have to copy-paste all the traits, which introduces the possibility of error, and precludes any easy way to follow (or even observe) the intended dependency.
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.
Research direction
No files, tests, or entry points are named. Start by surveying how the YAML descriptions are parsed and how specifications and traits are generated. The issue is complete only when a documented inheritance mechanism is defined and its behavior and dependency relationships are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100