Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Maya Binary Save that drops removed node records (prerequisite for hierarchy Delete)

Aperta
  • Qualcosa non va?
#272 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
backend, desktop

Direzione di ricerca

Start by reading the referenced issues #187, #228, and #246, then locate the existing staged-write transaction, source binding, dirty-scene guards, and save_scene path. The payload gives no file paths or tests to run, so trace those entry points and the proposed synthetic .mb fixtures first. Done means removed node records are omitted, untouched chunks remain byte-identical, the saved scene reopens correctly, and unsupported references produce typed errors without changing the destination.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area/file-io effort/xl impact/many priority/p2 severity/medium triaged type/feature urgency/this-quarter

Prerequisite for #187 slice 2 (real hierarchy Delete on opened scenes). Filed for the maintainer to prioritise.

Why

Hierarchy exists only in scenes opened from Maya files. Today NativeScene::remove refuses every node of a sourced scene, and #228 made that a specific typed error.

Allowing Delete in memory while refusing Save would leave a dirty scene that can never be saved. That is a trap, so the coordinator ruled it out (#187, option C). Real Delete on an opened .mb therefore needs Save to write the file without the removed records, while preserving everything else.

Scope (to be planned)

A Maya Binary save path that drops the IFF records of removed nodes from the retained source bytes and keeps every untouched chunk byte-identical:

  • the transform, its shapes and descendants;
  • the connectAttr / connection records that reference them;
  • any per-node chunks.

It reuses the existing staged-write transaction, source binding and dirty-scene guards. MCP gets the same path through save_scene.

Fidelity risks

  • Dangling references. Connections, sets, shading-group membership (instObjGroups), display or render layers, and selection sets can name a removed node. Each kind must be either rewritten faithfully or cause Save to refuse with a typed error. Nothing may be dropped silently.
  • Container size words and padding. Size words and alignment must be updated on every enclosing FOR8 chunk. The #246 splice work is related.
  • Node references. Records may refer to nodes by name or by index. Removing records must not change how the remaining records resolve.
  • Unknown or unsupported chunks inside a removed subtree must be dropped as a whole; anything outside the subtree must stay untouched.

Test strategy

  • Small synthetic .mb fixtures (distributable) covering a parent with children, a child, shapes with connections, and a material assignment.
  • For each fixture: remove a subtree, save, then
    • reopen and compare the scene graph;
    • byte-compare every chunk outside the removed records;
    • assert that refusal cases (unsupported references) return typed errors and leave the destination untouched.
  • Mutation probes on the size-word update and on reference handling.
  • An optional local differential against the private corpus. Nothing from that corpus is ever committed.
  • Maya reference: the Maya 2026 docs do not define file-level delete semantics, so behaviour is pinned by tests and marked PROVISIONAL.

Out of scope

  • Maya ASCII opened scenes, which stay read-only until a separate writer exists.
  • Instanced transforms with several parents, which stay refused.

Refs #187, #156

Lingua principale
Rust
Stelle
4
Fork
2
Merge medio
9h 16m
PR unite (30g)
179

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cristim/AztecCraft

Tutte le issue di cristim/AztecCraft

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.