Bug/57550 custom field with format version are ordered as strings 2 #17005
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
toy
force-pushed
the
bug/57550-custom-field-with-format-version-are-ordered-as-strings-2
branch
from
8514dd7
to
eb28def
Compare
toy
force-pushed
the
bug/57550-custom-field-with-format-version-are-ordered-as-strings-2
branch
from
eb28def
to
70644fc
Compare
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.
Ticket
OP#57550
What are you trying to accomplish?
Quick followup for #16776 that was merged prematurely, this includes the change to migration to use "universal"
undinstead ofencollation, removesorder_by_namescope.Another PR should handle cleanup of
Queries::Versions::Orders::NameOrderandQueries::Versions::Orders::SemverNameOrder, and remove special null handling for version, start date and due date columns.Merge checklist