-
Notifications
You must be signed in to change notification settings - Fork 697
feat(new): Add ability to set the newProperties #1721
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…he editProperties
@@ -87,7 +87,7 @@ const New: FC<ActionProps> = (props) => { | |||
record={record as RecordJSON} | |||
/> | |||
)) | |||
: resource.editProperties.map((property) => ( | |||
: resource.newProperties.map((property) => ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might also need to update where
to new
in BasePropertyComponent
and LayoutElementRenderer
. new
would then also have to be added to i. e. isVisible
for properties etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The where is used to determine the component to render in BasePropertyComponent
and we actually want to render the property with the edit component
@dziraf Any chance you have a look at this soon? |
Add ability to set the
newProperties
the same way we set theeditProperties