-
Notifications
You must be signed in to change notification settings - Fork 387
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
Fix for #1775 and #1760 #1781
Fix for #1775 and #1760 #1781
Conversation
Thanks for taking care of this issue!!! |
When will be this fix available? When we will have a new release? |
Waiting for #1726 |
Migrate from Original Dev Branch
@joelfmrodrigues any news about this issue? We hope to have a resolution |
Merge from Main Dev Branch to my personal dev branch
Sync the latest dev branch
Hi @joelfmrodrigues, why is this PR dependant on the #1726? It seems to be unrelated: editing filenames versus required fields showing a message. It would be nice if we could ditch the dependency and get this fixed soon. (I've got customers running into this as well...) If I can help with any of this, do let me know! |
Hey @martinlingstuyl I will have a look and likely merge this one as the other PR has unresolved conflicts for a long time. I haven't been active for a while for personal reasons (new kid and too much work 😅) but trying to get my head back into this and will try to look into this later today or over the weekend |
Great to hear @joelfmrodrigues! Yeah, personal reasons enough that can lower your available time in open source. also on my end recently. I know how it goes 😀 Do let me know if I can be of help... |
@wuxiaojun514 This is now merged. I'm really sorry for the time it took to merge |
@6gal6ler6 @devspfx @martinlingstuyl this is now merged, apologies for the delay |
That's great to hear @joelfmrodrigues! My customer is going to be super excited 😀 What's the release date for 3.20? |
@martinlingstuyl no date scheduled yet, but I will start the discussion on this as I can see there are several fixes/improvements already in this beta |
Maybe I can fix the PR assigned to me first.😊 I'll see if I can make haste there |
Hi @joelfmrodrigues, I now see why you related this pr to #1726: The testform now only works if I include FileLeafRef in the hiddenFields array. If I do not do that, submitting the form fails without an error. (due to the fact that the dynamic form currently cannot render What I'm now using in TestForm.tsx: <DynamicForm
context={this.props.context}
contentTypeId='0x0120D52000796BC7FCC8B819488729FB2B77B0E799002B2379630DCCB04D883603B763E843D7'
listId={this.props.context.list.guid.toString()}
listItemId={this.props.context.itemId}
hiddenFields={['FileLeafRef']}
onListItemLoaded={async (listItemData: any) => { // eslint-disable-line @typescript-eslint/no-explicit-any
console.log(listItemData);
}} /> FYI |
Ouch, I missed this, thanks for reporting back |
What's in this Pull Request?
This pull request is to fix two issues on required field validation issues in Dynamic Form control
Dynamic Form has done huge refactoring on version 3.17. See pull request 1672 for detail
The root cause of issue #1760 is due to the initial value of
newValue
has been changed from "null" to "undefined". So I modified the related code to "undefined" as well.Regarding #1775 , now
changedValue
won't use loaded item's value as initial value. So I added another check to compare withvalue
when there is no new value on this field.