Skip to content

Template validation enhancement: Validate string names and values against the expected defaults #7818

Open

Description

Is your feature request related to a problem? Please describe.

In dotnet/aspire#3190 some template localization content got left behind because the string keys and values weren't kept in sync.

Describe the solution you'd like.

It would be good to have a test helper or build validation that verifies:

  • all localization files have the same keys that are in the template.json file, and
  • the localization values in one language (default en) match those in the template.json file

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions