WIP: add back versionComment field #3134
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #
preview URL: https://add-back-versioncomment.loculus.org/
Summary
#2352 added the option to set a versionComment field for revisions and revocations. However, as revocations do not have original metadata fields I had to add a new column just for the versionComment for revocations. The versionComment in revisions should just be treated as a normal metadata field. However, the field in the column and in the metadata need to be merged in get-released-data and here the contents of the versionComment column were overwriting the contents of the contents of the metadata field - this PR fixes the merge problem.
Screenshot
Revisions work again - can be made via page and show up:
Revocations also still work:
PR Checklist