NG0300: Multiple components match node with tagname button: MatLegacyButton and MatButton error

[nilam-jadhav]

Describe the bug

I am using below JSON form package:
"@jsonforms/angular": "^3.0.0",
"@jsonforms/angular-material": "^3.0.0",
"@jsonforms/core": "^3.0.0",
Ans recently upgraded to Angular V15 where using legacy material component, after upgrading to V15 from, getting below error:

core.mjs:8400 ERROR Error: NG0300: Multiple components match node with tagname button: MatLegacyButton and MatButton. Find more at https://angular.io/errors/NG0300

Tried with v3.1.0 still issue persists.

After commenting JsonFormsAngularMaterialModule import, issue doesnt persist, but i need this import in my application so how to get rid of this error
can you help me to resolve this issue?

Expected behavior

Thre should not be any error

Steps to reproduce the issue

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots

No response

In which browser are you experiencing the issue?

Every

Which Version of JSON Forms are you using?

v3.0.0

Framework

Core, Angular

RendererSet

Material

Additional context

No response

[lucas-koehler]

Hi @nilam-jadhav ,
JsonForms 3.0.0 and 3.1.0 are not compatible with Angular 15+.
You can try pre-release version 3.2.0-alpha.4. This includes support for Angular 15.
I'll close this issue. You can re-open it if you continue having problems.

[sdirix]

We will update to Angular 16/17 very soon and therefore will no longer be compatible with Angular 15.

[nilam-jadhav]

Even after upgrading to mentioned version same issue is coming.

[nilam-jadhav]

@lucas-koehler I am not able to reopen this issue, can you please reopen? or Do I have to open new issue and link this one?

[lucas-koehler]

Hi @nilam-jadhav , sure. Just to be clear, when using Angular 16 or 17, did you also use the latest pre-release version 3.2.0-beta.0 when re-testing this?

[nilam-jadhav]

Hi @lucas-koehler
I am using Angular 15 with angular-material legacy component, and tried upgrading to version 3.2.0-beta.0 after your comment , now build is failing:

[lucas-koehler]

Hi @nilam-jadhav , after moving to 3.2.0-beta.0, did you also upgrade to Angular 16 or 17? Angular 15 does not work anymore with this.

[nilam-jadhav]

@lucas-koehler No, I haven't upgraded to Angular 16, its Angular 15 with 3.2.0-beta.0

[nilam-jadhav]

@lucas-koehler Any update?

[lucas-koehler]

@nilam-jadhav No, did you try it with Angular 16 and get the same result? It is not expected to work with Angular 15