Two refusals Makera Studio would not make: tabs on a circle, and a vise through-cut without a board
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- tauri, three.js, typescript
- Domain
- full-stack
Research direction
Start with the typical-jobs exercise at docs/bench/2026-10-27-z1-typical-jobs, case j12, and inspect the tab placement and through-cut clearance paths. The issue proposes allowing tabs on arcs and circles, while the vise behavior depends on measuring the low-profile vise lift as in #391 and deciding whether it satisfies the floor protection rule in #218. Done when the arc tabs work and the vise rule has a measured, documented decision.
Written by the indexing model from the issue text.
Description
From the off-bench typical-jobs exercise (docs/bench/2026-10-27-z1-typical-jobs, j12 aluminium medallion).
- Tabs on a round cut-out are refused (tab-unplaceable). Other CAM, Studio included, places tabs on arcs. Proposed: support tabs on arcs and circles.
- A through cut in the low-profile vise is refused without an under-board (through-needs-board). Makera's wiki (Low-Profile Vise) says the vise lifts the stock for through cuts. Our #218 rule protects the vise floor. Question: does the low-profile vise's lift give the clearance a breakthrough needs? If so, the vise's own lift should satisfy the rule, measured on the bench like the other vise numbers (#391).
Default if unanswered: keep the board rule for the vise, and do tabs on arcs.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No 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 SlyWombat/CaseMaker
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
bug
Difficulty 4/5 1-2 days Newbie friendliness 55/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
All issues in SlyWombat/CaseMaker
Similar issues
-
e2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 82/100
redhat-developer/rhdh-plugin-export-overlays#4616 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
ai-handle
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nextlevelbuilder/dewee-web-v2#73 ·
Maintainers usually reply within 1 day
-
backend bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
PoCInnovation/Distribox#255 ·
Maintainers usually reply within 1 day