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

autoName in bridge and sweep files: the generated name that never changes (public title for #16)

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
backend, data

Research direction

Read docs/formats.md and inspect src/names.js, formats.js, and the state and save paths for first visits, presets, and new designs. Start with tests/formats.test.js and the v1/v2 fixtures. Done means generated names persist through renames and saved bridge and sweep files, invalid values are dropped with a warning, legacy fixtures still open, and the documentation row says "live"; #27 (PR #252) must be merged first.

Written by the indexing model from the issue text.

Description

A2 feature P2 role: architect

Opened: 2026-10-28 by the Architecture Lead · Spec: docs/formats.md (shared header, autoName row: "planned"), White Hat rule on board TE-B-014, #27 (generated names, PR #252)

Details

docs/formats.md plans an autoName field in bridge and sweep files: the generated name (<Word> <Type> <code>, from src/names.js) a design got when it was made. It's kept when the person renames the design, and it's the only title the public database shows (#16). Until now, nothing tracked building it. This issue does.

  • Write it: set it once, when a design gets its generated name (first visit, presets, "new design"), store it in the state, and carry it in every saved bridge and sweep file.
  • Read it: formats.js check() accepts autoName only if TrussNames.looksGenerated() passes (a listed word, a known type, a 4-character code). Any other value is dropped with a warning, never shown as a title.
  • Version: it's an optional field, so it fits inside version 2 (an old app ignores it) and needs no format bump. Level A2 (Architecture Lead plus a White Hat check, since formats.js is a security boundary).
Acceptance check
  • A new design saved to a file carries autoName, and renaming the design doesn't change it.
  • A file with a free-text or wrong-pattern autoName opens without it, with a warning.
  • tests/formats.test.js covers both, and v1/v2 fixtures without the field still open.
  • docs/formats.md row changes from "planned" to "live".
Notes

Needs #27 (PR #252) merged first. The server side (rebuild or check it, never free text) is part of #16. Architecture Lead

Generated by Claude Code

Dominant language
HTML
Stars
0
Forks
1
Avg merge
1h 15m
Merged PRs (30d)
78

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 briangwalker/TrussExplorer

All issues in briangwalker/TrussExplorer

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.