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

Reopen: Fix import for Messages component - static template option #13899

Closed
aboudard opened this issue Oct 17, 2023 · 1 comment
Closed

Reopen: Fix import for Messages component - static template option #13899

aboudard opened this issue Oct 17, 2023 · 1 comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@aboudard
Copy link

Describe the bug

This is a reopen issue: #11575
The problem persists.
The original issue was created in version 13, this test was done in 16.

Environment

On a standalone component, the behavior is still the same, the SharedModule must still be imported when using the syntax for the Messages :

<p-messages severity="info" [closable]="false">
    <ng-template pTemplate>
      <div class="ml-2">Always bet on Prime.</div>
    </ng-template>
  </p-messages>

Link to the original stackblitz in version 13.

Reproducer

https://stackblitz.com/edit/stackblitz-starters-syy9t6

Angular version

16.2.9

PrimeNG version

16.5.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16+

Browser(s)

Chrome 118

Steps to reproduce the behavior

The exact same steps described in the original issue.

Expected behavior

No response

@aboudard aboudard added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Oct 17, 2023
Copy link

This issue has been automatically marked as stale due to a lack of activity. If this issue is still relevant to you, please leave a comment so we can keep it open. We apologize for not being able to prioritize it sooner. If you have any new information or questions, please share them in your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response 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

No branches or pull requests

2 participants