Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Attribute Editor

Open
  • Is something wrong?
#60 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
api, desktop

Research direction

Start with the Channel Box in src/app.rs and parity.md to see what generic attribute work is already pending. Also read .project-docs/mcp.md and its coverage inventory, since MCP tools and schemas must change in the same piece of work. Done means a tabbed Attribute Editor with disabled controls that state their reason, MCP protocol tests, a reviewed native screenshot, and failure tests that keep the baseline. Wait for the parity inventory and issue #5 before claiming any parity.

Written by the indexing model from the issue text.

Description

area/ui-parity in-progress type/feature

Problem

Only a Channel Box exists; no tabbed node attribute view.

Current behavior

Channel Box in src/app.rs; generic attributes are pending per parity.md.

Expected behavior

Attribute Editor panel with node tabs and sections for supported nodes, sharing typed attribute operations with MCP. The per-element Autodesk Maya 2026 doc links are being collected in the UI parity inventory (slice A, in progress); add them here when it lands.

Acceptance criteria

  • 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.
Dominant language
Rust
Stars
4
Forks
2
Avg merge
2h 28m
Merged PRs (30d)
76

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cristim/AztecCraft

All issues in cristim/AztecCraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.