Skip to content
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

Default values doesn't work for properties of objects in array #1327

Closed
3 tasks done
ketysek opened this issue Jun 20, 2019 · 6 comments
Closed
3 tasks done

Default values doesn't work for properties of objects in array #1327

ketysek opened this issue Jun 20, 2019 · 6 comments
Labels
bug core possibly close To confirm if this issue can be closed

Comments

@ketysek
Copy link

ketysek commented Jun 20, 2019

Prerequisites

  • I have read the documentation;
  • In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.
  • I'm providing a shared playground link demonstrating the issue.

Description

Default value doesn't work for properties of objects in array, they get erased from the formData instead.

Steps to Reproduce

I've created a playground here, where you are free to try it.

Expected behavior

Once you remove a values from fields Client secret or Bulls -> Name, it works as expected and you can see the default empty strings in formData for these properties. But when you erase the value from Search -> Name field, you'll get empty object in search array instead of object with default name as empty string (as specified).

@epicfaace
Copy link
Member

Thanks for reporting. Do you know if this worked before 1.6?

@ketysek
Copy link
Author

ketysek commented Jun 21, 2019

@epicfaace I can tell you only that it doesn't work even in version 1.1.0 which we have installed in our app.

@heath-freenome
Copy link
Member

@ketysek I cannot reproduce this with the latest 5.x playground. Can you verify if this is fixed?

Copy link

stale bot commented Jul 9, 2024

This issue has been automatically marked as possibly close because it has not had recent activity. It will be closed if no further activity occurs. Please leave a comment if this is still an issue for you. Thank you.

@stale stale bot added the possibly close To confirm if this issue can be closed label Jul 9, 2024
Copy link

stale bot commented Aug 9, 2024

This issue was closed because of lack of recent activity. Reopen if you still need assistance.

@stale stale bot closed this as completed Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug core possibly close To confirm if this issue can be closed
Projects
None yet
Development

No branches or pull requests

5 participants