Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Native Extrude control with manipulator, region and all-face extrusion

Abierto
  • ¿Algo no está bien?
#44 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
api, desktop

Línea de trabajo

Start with known-issues.md under "Core authoring limits" and the existing core Extrude API and MCP tool, then read .project-docs/mcp.md and its coverage inventory. The first blocker is the pinned Maya fixture from #5, which must define all-face extrusion before any behavior is implemented. Done means the native control, MCP schemas, Editor protocol tests and a reviewed window screenshot all agree with that reference, and unverified constants are marked provisional.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area/modeling type/feature

Problem

Extrusion exists as a core API and MCP tool only; the native control is disabled.

Current behavior

known-issues.md ("Core authoring limits"): one quad, signed object-space displacement; all-face (including one-quad plane) extrusion is unsupported until a pinned fixture defines default behavior; region/world extrusion, divisions, offset/taper, UVs/normals and construction-history nodes pending.

Expected behavior

Native Extrude with a manipulator workflow and history, then region/world extrusion and options, matching the pinned reference.

Acceptance criteria

  • Default behavior for all-face extrusion taken from a pinned Maya fixture.
  • Unimplemented controls stay visibly disabled with a reason; no dummy tools or controls.
  • MCP coverage in the same change: implemented operations and relevant state exposed with synchronized tool schemas, real Editor protocol tests (scene token, draft, modal, close and busy guards) and updates to .project-docs/mcp.md and its coverage inventory.
  • Native visual check of the real window (screenshot reviewed), not only headless tests.
  • Tests cover malformed, empty, boundary and failure cases; failed operations preserve the baseline.
  • No parity claim without comparison against the pinned Maya reference (#5); unverified constants are documented as provisional.
Lenguaje dominante
Rust
Estrellas
4
Forks
2
Merge medio
6 h 23 min
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cristim/AztecCraft

Todos los issues de cristim/AztecCraft

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.