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 modified index is not reindexed when the object gets updated #1809

Merged
merged 3 commits into from
May 28, 2021

Conversation

xispa
Copy link
Member

@xispa xispa commented May 28, 2021

Description of the issue/feature this PR addresses

The index modified does not get reindexed after an object is updated. It always store the value when the brain was created in first place.

This can be easily tested by transitioning a sample (e.g. cancel or invalidate) and then check with the jsonapi as follows:
http://localhost:9090/senaite/@@API/senaite/v1/analysisrequest?recent_modified=today

It might require #1808 to be merged first

Current behavior before PR

The modified index is not reindexed when the object gets updated

Desired behavior after PR is merged

The modified index is reindexed when the object gets updated

--
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.

xispa added 2 commits May 28, 2021 17:47
The index `modified` does not get reindexed after an object is updated. It
always store the value when the brain was created in first place.
@xispa xispa requested a review from ramonski May 28, 2021 16:09
@ramonski ramonski merged commit 23ed997 into 1.3.x May 28, 2021
@ramonski ramonski deleted the reindex-modified branch May 28, 2021 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants