Zoltán Lehóczky

Same or related? https://github.com/OrchardCMS/OrchardCore/issues/17985

Maybe not with an ApiControllet but a potentially more efficient minimal API endpoint, see e.g. https://github.com/OrchardCMS/OrchardCore/tree/main/src/OrchardCore.Modules/OrchardCore.Contents/Endpoints/Api. See rationale and metrics: https://github.com/OrchardCMS/OrchardCore/pull/15294.

Have you tried adding a second, custom driver (a part/field can have any number of drivers)?

You can display the same shape from your own driver too, with a different differentiator (to be able to target it from placement, see `ShapeResult.Differentiator()`), and hide the original one...

These are both better done from `IShapeTableProvider`: - `AdminAttribute.IsApplied()` check: you can hide (place) shapes with any custom logic, see an example [here](https://github.com/Lombiq/Orchard-Training-Demo-Module/blob/0684bb884fdc86c510422cc7bc5f4b786899e9bc/Lombiq.TrainingDemo/Services/ShapeHidingShapeTableProvider.cs#L43). - Customize label: in `OnDisplaying` you can...

> How do I know if the shape is for a new contentitem? And second, I'd need access to parent part settings, is that possible? That was pretty straightforward from...

If you implement `IContentDisplayHandler.BuildEditorAsync()`, which is an extension point (much like content part handlers) for use cases like yours, then you can access `IsNew` as well, since it receives `BuildEditorContext`.

So, I don't think any change should be needed for your use case, let alone in general in the magnitude of https://github.com/OrchardCMS/OrchardCore/pull/16898. So, please tell why you think it's still...

Thank you! Please update your PR with: > As for PR, I would omit the TypePartDefinition but would keep the IsNew flag for better developer experience if anyone wants to...

As in, omit TypePartDefinition in the PR.