EZP-28949: switched sort of field type selection to use human readable name #216
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
webhdx
approved these changes
Mar 14, 2018
|
@skonrad could you make a JIRA ticket and amend PR title and commit? We can include this improvement in 2.1 release for March 26th. |
skonrad
changed the title
|
@lserwatka The ticket is created and I adjusted the commit-messages and pr-title accordingly. |
|
@skonrad thank you. |
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.
Field types are currently sorted by their respectable identifiers (e.g. ezstring, eztext, etc.)
This works fine with the default build in field types but degrades UX once custom field types are introduced.