Spec points to a [platforms.<id>] reference it does not contain; CLI error and doc comments still say top-level `manifest`

Open Beginner friendly
#1,744 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown, rust
Domain
cli, documentation

Research direction

Start with packages/design-data-spec/spec/dataset-layout.md and spec/manifest.md, then review the error in sdk/cli/src/main.rs and comments in sdk/core/src/manifest.rs. Update the configuration reference and link, and align the error and comments with the supported platform options; done when all four locations describe [platforms.<id>], default_platform, --platform, and the legacy manifest key accurately.

Written by the indexing model from the issue text.

Description

design-data-spec

Summary

The spec points readers to a .design-data.toml reference for [platforms.<id>] profiles that it does not contain, and the CLI error text and two doc comments still describe only the legacy top-level manifest key.

Spec

  • packages/design-data-spec/spec/manifest.md:91 says several manifests are configured via named [platforms.<id>] profiles, "see the SDK's .design-data.toml reference". There is no link, and spec/dataset-layout.md:48 and :60 describe only [source], [cache] and the top-level manifest. [platforms.<id>] and default_platform are documented only in platforms/README.md and docs/site/src/articles/configuring-design-data-for-your-platform.md.

CLI and doc comments

With a [platforms.rune] entry and no default_platform, design-data validate-manifest (CLI 0.31.0) says:

design-data: error: no platform manifest configured (set the `.design-data.toml` top-level `manifest` key, or pass --manifest <FILE>)

It doesn't mention [platforms.<id>], --platform or default_platform.

  • sdk/cli/src/main.rs:2372-2373: the message above.
  • sdk/core/src/manifest.rs:14 and :277-278: module and function docs say "top-level manifest key".

(The SourceConfig doc comments in sdk/core/src/data_source/mod.rs:109 and :132 already mention [platforms.<id>].)

Suggested fix

Document [platforms.<id>] and default_platform in dataset-layout.md and link it from manifest.md:91; reword the error and the two doc comments to name [platforms.<id>], --platform and the legacy manifest key.

Dominant language
Rust
Stars
157
Forks
37
Avg merge
6h 30m
Merged PRs (30d)
187

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 adobe/spectrum-design-data

All issues in adobe/spectrum-design-data

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.