Brick extraction: OBJ importer
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- csharp
- Domain
- build-system, release
Research direction
The payload names no files or entry points, so start from the split made by #47 and find where the OBJ importer's code currently lives in the MASS4ORG/Turian repository. Check whether it already has its own repository or published package, and list its remaining references to core types. Done means the importer is released as an independent package, Turian consumes that published package, and CI rejects boundary violations. Confirm the scope with maintainers before starting, since the first task is an open investigation.
Written by the indexing model from the issue text.
Description
Current State
The OBJ importer was split from the core by #47. It is not established whether it already has its own repository, release cadence and CI boundary check.
Tasks
- Confirm the remaining coupling to core types
- Move it to its own repository and publish it as a package if it is not there yet
- Consume the package from Turian and enforce the boundary in CI
Acceptance Criteria
- The OBJ importer is released independently and Turian consumes the published package.
Related
#47, brick extraction epic
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 29m
- Merged PRs (30d)
- 38
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from MASS4ORG/Turian
-
c:assets p:low size:XS t:task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
c:build p:high size:L t:feature
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
c:build c:editor p:medium size:XL t:feature
Difficulty 5/5 Over a week Newbie friendliness 5/100
Maintainers usually reply within 1 day
-
c:build p:medium size:XL t:refactor
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
c:build c:ui p:low size:L t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
dette technique priorité: basse zone: service
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
damiensabau/nexus-lobby#25 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sebastienros/jint#4282 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
pyrevitlabs/pyRevit#3792 ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-product-decision clawsweeper:needs-security-review clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security impact:ux-friction issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
openclaw/openclaw-windows-node#1763 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day