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

fix: (core) DatePicker - fix form's valid flag, when allowNull #1609

Merged
merged 2 commits into from
Nov 20, 2019

Conversation

JKMarkowski
Copy link
Contributor

@JKMarkowski JKMarkowski commented Nov 15, 2019

Please provide a link to the associated issue.

fixes: #1598

Please provide a brief summary of this pull request.

Right now I check if the input is empty and allowNull flag is added. Also there was some minor bug on datepicker, which is fixed now.

Please check whether the PR fulfills the following requirements

This is only fix PR, without any new things. So no docs needs to be changed.

Documentation checklist:

@JKMarkowski JKMarkowski added this to In progress in Development via automation Nov 15, 2019
@JKMarkowski JKMarkowski added this to the sprint 24 - Maester Aemon milestone Nov 15, 2019
@netlify
Copy link

netlify bot commented Nov 15, 2019

Deploy preview for fundamental-ngx ready!

Built with commit 7d0fe76

https://deploy-preview-1609--fundamental-ngx.netlify.com

@droshev
Copy link
Contributor

droshev commented Nov 17, 2019

@JKMarkowski can you put (core) after :?

@JKMarkowski JKMarkowski changed the title fix(core): fix form's valid flag, when allowNull fix: (core) fix form's valid flag, when allowNull Nov 18, 2019
Development automation moved this from In progress to Reviewer approved Nov 19, 2019
* 0, when none,
* 1, when only startDate, or endDate same as startDate,
* 2, when both
* 0, when none of selected, or start date is invalid,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My English is not good, but doesn't this mean exactly the same as point 2? (both are valid)
@stefanoScalzo some help here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be
0, when selected and startDate are valid
1, when given valid startDate and endDate is same as startDate

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It has been changed, please take a look on it now.

* 1, when only startDate, or endDate same as startDate,
* 2, when both
* 0, when none of selected, or start date is invalid,
* 1, when only startDate, or endDate same as startDate, but startDate is valid,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here I am lost ...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It has been changed :)

@JKMarkowski JKMarkowski changed the title fix: (core) fix form's valid flag, when allowNull fix: (core) DatePicker - fix form's valid flag, when allowNull Nov 20, 2019
@InnaAtanasova
Copy link
Contributor

Perfect!

@JKMarkowski JKMarkowski merged commit df066e1 into master Nov 20, 2019
Development automation moved this from Reviewer approved to Done Nov 20, 2019
@JKMarkowski JKMarkowski deleted the fix/#1598-datepicker-allownull branch November 20, 2019 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DatePicker control does not support null or empty values and the Control and Form are invalid.
4 participants