primeng Resolved issue 10963 in panel menu

###Defect Fixes When submitting a PR, please also create an issue documenting the error.

###Feature Requests Due to company policy, we are unable to accept feature request PRs with significant changes as such cases has to be implemented by our team following our own processes.

Mar 31 '22 09:03 NilavPatel

Solution for defect https://github.com/primefaces/primeng/issues/10963

Mar 31 '22 09:03 NilavPatel

Sigo esperando la solución para este defecto. Por el momento reemplace ese componente por el SLIDEMENU, por si a alguien le sirve como solución temporal. Gracias.

Jun 22 '22 16:06 rodolfocipagauta

Hi @NilavPatel will this problem be fixed in the near future?

Jun 24 '22 08:06 ColinNor

Not sure, I have created pull request with solution, but no one has review and merge it.

Jun 24 '22 08:06 NilavPatel

Do you have any news on this one?... for us, this issue will define a go/no go with the latest version or keep PrimeNG version 9... the bad thing is that we bought the theme designer to do the migration, and now we are very disappointed since we have lots of panel menus inside sidebars :( !!

Aug 03 '22 21:08 Zagano-AOR

@yigitfindikli would you please take a look at this merge request? Lots of peoples are facing this issue now.

Aug 04 '22 05:08 NilavPatel

I sent a mail to support and was told that this issue will be fixed in the next release

Aug 04 '22 05:08 ColinNor

Really, excellent news... I just can't wait

Aug 04 '22 21:08 Zagano-AOR

<p-sidebar [(visible)]="visibleSidebar"  >
    <p-panelMenu *ngIf="visibleSidebar" [model]="modulos" autoDisplay="true"></p-panelMenu>
</p-sidebar>[](url)

lil trick, use same boolean for visible with ngif in panelMenu, have visual bug but works

Jan 13 '23 22:01 AlexAvilaSantos

Hi @NilavPatel,

Thanks a lot for your first-time contribution! Don't forget to run npm run build:check command before pushing changes.

Jan 26 '23 11:01 cetincakiroglu