donmccurdy / donmccurdy/glTF-Transform
Consider moving 'property-graph' into glTF Transform
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 206
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
I wrote property-graph as the underlying graph data model for glTF Transform. It's an external repository because it's generalized enough for other uses, but in practice I think it's only used by glTF Transform, 5 years in.
For easier maintenance (and a no-runtime-dependency core) I think it could make sense just to move the property-graph codebase into glTF Transform.
Contributor guide
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 comparing the external property-graph repository linked in the issue with the glTF Transform repository and identifying how glTF Transform currently uses it. Done means the property-graph codebase is incorporated into glTF Transform, maintenance is consolidated, and the core has no runtime dependency on the external repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- computer-graphics
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100