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 date and datetime required validations issue #7198
Conversation
Signed-off-by: soupette <cyril.lpz@gmail.com>
Codecov Report
@@ Coverage Diff @@
## master #7198 +/- ##
==========================================
- Coverage 26.17% 26.17% -0.01%
==========================================
Files 1130 1130
Lines 15406 15410 +4
Branches 2436 2438 +2
==========================================
Hits 4033 4033
- Misses 9557 9559 +2
- Partials 1816 1818 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
LGTM. @ralphsomeday does that fix your issues ?
@alexandrebodin this should fix it :)! thanks. I guess you will be releasing it in 3.1.2, right? |
Just updated to 3.1.2. Issue with required boolean values remains as described above. |
@pjamieson did you rebuild your admin ? |
Yes. I have both re-installed with yarn and rebuilt Strapi with yarn develop. (And I see the same issue in a production build.)
Originally, I was running 3.0.5, and did not have this issue with the required boolean values. The problem started when I updated to 3.1.1, and remains after updating to 3.1.2.
When I initially try to save an update, the boolean values (I have 3 required boolean values in this case) are flagged as required in the UI, even though they were previously set and have not been touched. Toggling them makes the warning in the Admin UI go away, but saving still does not work, and validation errors still appear in the Chrome Dev Tools.
FYI, in one case (with v3.1.1) a required decimal value (for a price) appeared to exhibit the same problem even though it already had a previously entered valid entry of 0.00. I have not dug into that one, as I have been focused on the booleans.
Thanks for looking into this.
Patrick Jamieson
… On Jul 30, 2020, at 12:42 AM, Alexandre BODIN ***@***.***> wrote:
@pjamieson <https://github.com/pjamieson> did you rebuild your admin ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#7198 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADT5HKVBJ37EW3WYSTIR4DR6EP5FANCNFSM4PISXIZA>.
|
Signed-off-by: soupette cyril.lpz@gmail.com
Description of what you did:
This PR fixes the required validation issue when updating a entry that has a required date field.