More flexible SpaceWarp dependency checking #3858
Merged
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
HebaruSan
added
Enhancement
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.
Motivations
Some KSP2 modules have started using a new format for the
dependencieslist inswinfo.json, and a few don't match the capitalization of the identifier in CKAN:Currently we warn if the string doesn't match the identifier of any value in the
dependslist, so these will always warn even if you haveSpaceWarporUITKforKSP2in there.Changes
Now we remove characters up to and including the final
., then perform a case-insensitive comparison. This will produce fewer false positive warnings.I might self-review this since it's just a Netkan warning.