-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Unchecking isAllDay
has no effect
#463
Comments
Set |
Maybe you mis-understood, but what I mean is not changing the |
I recommend to use |
Thanks @mariusa, but that will definitely defeat the purpose of having But for now it make sense to use |
Right. There is a proposal to remove 'isAllDay'
…On Tue, Nov 26, 2019, 16:25 WilliamWsyHK ***@***.***> wrote:
Thanks @mariusa <https://github.com/mariusa>, but that will definitely
defeat the purpose of having isAllDay from the start, i.e. why the team
create such property if you are not intentionally change its value when
there is updates on the field? This is just confusing.
But for now it make sense to use category === 'allday' to check, provided
that the update will populate the changed value.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#463?email_source=notifications&email_token=AAJZOASJZG4BJQD4BVYJTZLQVUWURA5CNFSM4JNKZ672YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFGFYVI#issuecomment-558652501>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJZOAUDX4YUSL2USSXSHFTQVUWURANCNFSM4JNKZ67Q>
.
|
@WilliamWsyHK I'll fix it in the next patch version. |
fix: check defined properties on beforeUpdateSchedule(fix #463)
Version
1.12.7
Development Environment
Windows IE 11 and Chrome 78
Current Behavior
Unchecking
isAllDay
has no effect. ThebeforeUpdateSchedule
does not populate any changes whenisAllDay
is unchecked.Expected Behavior
isAllDay === false
if the user has click to uncheck the all day checkbox.The text was updated successfully, but these errors were encountered: