Skip to content

packs: improve local addon import validation messages #8

@Senzo13

Description

@Senzo13

Context

Local addons are important for extensibility, but pack import errors should be actionable for people creating their first pack.

Relevant files:

  • core/infra/packs.py
  • web/routes/settings.py
  • web/static/js/settings.js
  • tests/test_packs_smoke.py

Suggested approach

Improve errors for missing pack.json, invalid JSON, missing referenced asset files, unsupported kind, and duplicate pack IDs.

Acceptance criteria

  • Backend errors identify the exact missing/invalid file when possible.
  • UI displays a concise human-readable message.
  • At least one test covers an invalid pack folder.
  • Existing pack smoke tests pass.

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomerspacksLocal addons and pack validationtestsAutomated tests and regression coverageuiUser interface polish and behavior

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions