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

Use modified_at in Task to ensure the last write wins #1037

Merged
merged 1 commit into from
Oct 10, 2017

Conversation

joshsmith
Copy link
Contributor

@joshsmith joshsmith commented Oct 9, 2017

What's in this PR?

This simply adds a custom validation to the Issues.ChangesetBuilder that checks whether the modified_at is after the modified_at we're trying to set, and if so, then errors.

References

Fixes #1035
Fixes #1036

@joshsmith
Copy link
Contributor Author

One thing I don't like about this is that I had to change e.g. in all the JSON 2015 to 2075 as a far-future enough date for us to have the modified_at changeset validation not be an issue. This is pretty hidden behavior and causes the errors to be rather difficult to parse sometimes.

begedin
begedin previously approved these changes Oct 10, 2017
Copy link
Contributor

@begedin begedin left a comment

Choose a reason for hiding this comment

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

Not much to say about this one. Clean and straightforward 👍

@joshsmith joshsmith merged commit a80045c into develop Oct 10, 2017
@joshsmith joshsmith deleted the 1035-modified-at-task branch October 10, 2017 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants