Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Component: Messages Spelling #14009

Closed
jacver opened this issue Nov 2, 2023 · 0 comments · Fixed by #14008
Closed

Component: Messages Spelling #14009

jacver opened this issue Nov 2, 2023 · 0 comments · Fixed by #14008
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@jacver
Copy link
Contributor

jacver commented Nov 2, 2023

Describe the bug

Describe the feature you would like to see added

Not a defect in the programmatic sense which would result in an useless bug report, so consequently expressed as an improvement request.
I found a typo which is fixed in a PR.

Is your feature request related to a problem?
No response

Describe the solution you'd like
No response

Describe alternatives you have considered
No response

Additional context
No response

Environment

N/A

Reproducer

No response

Angular version

16.2.10

PrimeNG version

16.7.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.7.1

Browser(s)

No response

Steps to reproduce the behavior

  1. Go to src/app/showcase/doc/messages/closabledoc.ts
  2. View this array:
this.messages2 = [
            { severity: 'warn', summary: 'Waning', detail: 'Closable Message Content' },
            { severity: 'warn', summary: 'Warning', detail: 'Closable Message Content' },
            { severity: 'error', summary: 'Error', detail: 'Closable Message Content' }
        ];

In the first Summary key, there is a typo where Waning is incorrectly typed.

Expected behavior

When searching for an expected string, you are able to find it because there is no typo.

@jacver jacver added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant