Sanity Checking Overhaul
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Currently, sanity checking and exporting happen in the same step. Due to the arbitary order of the export process, this causes sanity checking to be duplicated in many locations. Perhaps a new step in the exporter that calls each object's (and its modifiers') dedicated sanity check routines should be introduced. Furthermore, modifiers need to have better error reporting facilities, much like the raise_error method on Nodes.
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 tracing the exporter’s current sanity-checking and export flow, including the object and modifier routines mentioned in the issue. Done should mean sanity checks run in a dedicated exporter step without duplication, and modifiers provide error reporting comparable to the Node raise_error method.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blender, python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100