Closed uwaheed88 closed 4 years ago
@uwaheed88 we should have probably discussed this better before you implemented a fix, because I don't think the approach you took is correct. Our goal is not to create different revisions (with the same content) so each tag has it's own revision ID. That goes against the model of revisioning / tagging that we want to take.
Our fix should be on the GUI level - the GUI should be aware that we are looking at a tag and what the tag is, and not just have the revision ID in the URL / state. This will resolve this issue in a much cleaner way. Basically, a good fix for this will probably not need to touch anything in the logic / actions level, only modify templates and helpers (most likely).
In addition, please note that CI is failing for this PR. In the future a PR should not be marked as ready for review if CI fails.
I'm closing this for now, if you want to discuss the solution I'm suggesting please ping me, otherwise you can just open a new PR with a better fix.
Issue: IVT-2794
dataset_tag_create
method inaction.py
to make new revision_id for every tag that is going to be created whether the dataset is updated or not.