update GeMS_ValidateDatabase.py sorts problematic map units in ValidationErrors.html alphabetically #105
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.
Prepended the text '2.5' to 'Duplicated MapUnit values in DescriptionOfMapUnits' to match the other rule violations when displayed in ValidationErrors.html.
Added sort_mapunit_errors function and called it for Rules 2.4, 2.5, 3.8, and 3.9, which should satisfy this enhancement request: Sort DMU output in Validate Database report by HKey or alphabetically? #99 (comment)