Fix regex for parsing difficulty data - #24
Open
tsweet64 wants to merge 1 commit into
Open
Conversation
|
Yup. Preety simple fix. Please add this. |
JonasNau
approved these changes
Nov 9, 2022
This file contains hidden or 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
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.
I experienced an issue where parsing the .osu files failed due to the
match()returningnull. This seems to have been because my files had spaces separating the keys and values, likeHPDrainRate: 3instead ofHPDrainRate:3and because some values were pure integers with no decimals (I use osu!lazer, so perhaps these are differences from the stable version). This commit updates the regex to accommodate files with or without spaces, and values with or without decimal points.