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.
Problem
It was a surprise to see this for an established mod that probably isn't changing much from one release to the next:
It seems like the warning should remain the same and therefore not be sent to Discord.
Cause
Same files, different order. The order of the list in the message depends on the order in the ZIP file, so if a succession of releases has the same warnings but the ZIP is created slightly differently, we get extra warning messages sent to Discord:
This could happen for any warning that contains a list of multiple things.
Changes
Now the following messages are sorted alphabetically. This will probably cause a one-time cascade of new warnings sent to Discord as they all switch over to the proper sorted order:
Also the
localizations
property will now be in alphabetical order. This might cause a large number of one-time re-indexings.