The source project of this merge request has been removed.
WIP: Just clear the markdown cache when saving objects
What does this MR do?
Changes the behaviour of object.save
so markdown cache columns are cleared, rather than updated
Are there points in the code the reviewer needs to double check?
We're moving work from the update phase to the first view phase. Since we generally redirect the updater back to view their own content, this will be a no-op most of the time, although I'm unsure about highly concurrent viewing scenarios.
Why was this MR needed?
In https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1708 we discovered that the existing behaviour breaks some specs in a hard-to-understand way.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together