How to handle different bl_info metadata categories?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The category in bl_info is set to Object in the init.py file in the randomiser folder. This is used by materials, transforms and geometry which may have different categories so how do we handle this?
If it's simply a way to filter the add-ons then it may be an unimportant issue, but if it affects which categories we can operate on then we may need to re-think this.
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
Start by reading init.py in the randomiser folder and inspect how bl_info sets the Object category. Compare the materials, transforms, and geometry components to determine whether one category is appropriate or whether separate handling is needed. Done means documenting the metadata behavior and agreeing on a concrete category strategy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100