Skip to content

Localization support for constants #79

@Lewiscowles1986

Description

@Lewiscowles1986

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

While working on #77 I introduced a constant to the library, which would embed English within the component. For non-English speakers this might represent a problem, or inconsistency with the announced highlighted option.

Describe the solution you'd like

Ideally for the problem introduced, a new piece of state could be introduced to allow user-supplied values for these constants, which have default values.

Describe alternatives you've considered

Library locale aware

The library could become locale aware, and locale could be sent in as state.

This might help other efforts, such as requesting localized results from a remote server. As user-js is needed to bootstrap plete, this was already possible, and might be something for Plete to avoid.

Differentiation of highlighted items could be removed

#78 could remove the differentiation and just announce the item without a custom aria-label.

Motivation and involvement

  • I / My organization is willing to commit to development and maintenance of this feature / request
  • [] I / My organization wish to financially contribute to the development of this feature / request
  • This would be nice to have, but I wish to have no involvement

Proof of concept

There is not, but it's an optional configuration value passed around with state context.

Additional context

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions