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

Improve locked date management in task updates #499

Merged
merged 2 commits into from
Sep 14, 2021

Conversation

jaragunde
Copy link
Member

Fixes #487 and #491.

We were only checking the new task date in a task update operation,
instead of also checking the saved date. As a result, it was
possible to move a task from a locked date to an unlocked one, and
then update any other field.

As a side effect, we break the assumption in PartialUpdateTasksAction
that every DirtyTask contains a date, which helps fixing #491.
Ensure that date field is extracted from the saved task in case the
DirtyTaskVO does not contain it.

Also use array_key_first() to get the first task in the list, because
a list of tasks where some were discarded might not start with 0. PHP
version in the requirements has been bumped to 7.3.0 due to this.
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.

Update task service should not require the date field
1 participant