Vincenzo Scamporlino

> @stephenglass thanks for raising this PR! > > I think that this is one of many improvement PR's that have been raised over the last few weeks with regards...

Closed by https://github.com/backstage/backstage/pull/29584

I think this will be fixed next week once Backstage 1.33 will be released. In the meantime I recommend you to use node 20.

Hey @CptnFizzbin, just a small suggestion to make reviews easier - try to avoid moving or refactoring stuff unless it’s really needed for the changes. It can make the review...

Can you share the template you are trying to add? in your reproduction steps you need to double check that the fields for the template are valid (switching `kind` isn't...

Using the search plugin is probably a better option than using the catalog for searching if you have such complex entities

I answered this time ago on Discord. At the moment the only way to achieve this is to wrap the routes in a `RequirePermission`: ```tsx const defaultEntityPage = ( {somecontent}...

try to move `EntityLayoutWrapper` down: ```tsx const serviceEntityPage = ( {overviewContent} {cicdContent} ... ```

ah sorry my bad, in `errorPage` prop I put `EntityLayout` as child of `EntityLayoutWrapper` which is not allowed. this should be correct: ```tsx const serviceEntityPage = ( {overviewContent} {cicdContent} ......

Closing this as we want to stick with material-ui v4 for the moment.