-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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: improve CM modified date comparison #19898
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thanks! Makes sense to me. I've merged this into #20258 to check the CI on the tests I was having trouble with. I'll approve if everything works |
@jhoward1994 tests were not passing here at the time, so mayabe it's still not enough, but let me know if you want to work on it together! |
Okay thanks. I'm working on it a bit in #20258. Sorry it breaks our PR organisation a bit but I need to test it with the e2e tests in that branch. I can cherry pick it here so we can trace it all |
packages/core/content-manager/server/src/services/document-metadata.ts
Outdated
Show resolved
Hide resolved
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.
nice! thank you for the work Jamie, lets push to fix all api tests and we can merge this. Let me know if we want me to jump in a call at any time!
What does it do?
Remove the clunky date check for Modified status, now , when publishing on the document service, we assign the updated value of the published version to be exactly the same as the publish version.
Before they were not "exactly" the same, (off by milliseconds) and we had to add a threshold for the check
Reopened from #19787