Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add test case covering stability of compatibility export operation #30795

Merged

Conversation

bdach
Copy link
Collaborator

@bdach bdach commented Nov 20, 2024

This is important as the format will be used more when lazer beatmap submission comes online, and its stability is a useful property for that.

Included archive contains an .osu with a few fractional-millisecond timing points and objects, fractional-coordinate positions, as well as a multi-segment-type slider. That should cover the range of all possible modifications that the compatibility exporter currently performs.

This is important as the format will be used more when lazer beatmap
submission comes online, and its stability is a useful property for
that.

Included archive contains an `.osu` with a few fractional-millisecond
timing points and objects, as well as a multi-segment-type slider. That
should cover the range of all possible modifications that the
compatibility exporter currently performs.
@bdach bdach added the area:beatmap-parsing .osu file format parsing label Nov 20, 2024
@peppy peppy self-requested a review November 20, 2024 16:39
@peppy peppy merged commit ba21ad2 into ppy:master Nov 20, 2024
7 of 10 checks passed
@bdach bdach deleted the compatibility-export-stability-test-coverage branch November 21, 2024 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:beatmap-parsing .osu file format parsing size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants