Open-source web application framework for ASP.NET Core! Offers an opinionated architecture to build enterprise software solutions with best practices on top of the .NET. Provides the fundamental infrastructure, cross-cutting-concern implementations, startup templates, application modules, UI themes, tooling and documentation.
Is your feature request related to a problem? Please describe the problem.
As a developer
I want to be able to use the record field in PropPredicate and PropCallback properties on Create forms
So that I can dynamically set, for example, the disabled property based on the value of other properties that are currently set in the create form
Describe the solution you'd like
The syntax would remain identical to how it is now, only that it would actually work. It should be such that the documentation can be changed to say that the record field (and others?) are available on create forms (e.g. create user).
https://docs.abp.io/en/abp/latest/UI/Angular/Dynamic-Form-Extensions
For example, a new extra property that I add to the form can be disabled or enabled based on whether the user has checked IsActive or not.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
As a developer I want to be able to use the
record
field inPropPredicate
andPropCallback
properties on Create forms So that I can dynamically set, for example, the disabled property based on the value of other properties that are currently set in the create formDescribe the solution you'd like
The syntax would remain identical to how it is now, only that it would actually work. It should be such that the documentation can be changed to say that the
record
field (and others?) are available on create forms (e.g. create user). https://docs.abp.io/en/abp/latest/UI/Angular/Dynamic-Form-ExtensionsFor example, a new extra property that I add to the form can be disabled or enabled based on whether the user has checked IsActive or not.
Additional context
No response