osu-lazer/osu.Game.Rulesets.Osu/Resources/Testing/Beatmaps/slider-ticks-edge-case-expected-conversion.json

{
  "Mappings": [
    {
      "StartTime": 7493.0,
      "Objects": [
        {
          "StartTime": 7493.0,
          "EndTime": 7493.0,
          "X": 130.0,
          "Y": 232.0,
          "StackOffset": {
            "X": 0.0,
            "Y": 0.0
          }
        },
        {
          "StartTime": 7817.0,
          "EndTime": 7817.0,
          "X": 30.9946651,
          "Y": 208.5157,
          "StackOffset": {
            "X": 0.0,
            "Y": 0.0
          }
        },
        {
          "StartTime": 7843.0,
          "EndTime": 7843.0,
          "X": 33.7820168,
          "Y": 208.9957,
          "StackOffset": {
            "X": 0.0,
            "Y": 0.0
          }
        }
      ]
    }
  ]
}
Add test coverage of failing slider tick generation edge case 2023-09-07 17:20:07 +08:00			`{`
			`"Mappings": [`
			`{`
			`"StartTime": 7493.0,`
			`"Objects": [`
			`{`
			`"StartTime": 7493.0,`
			`"EndTime": 7493.0,`
			`"X": 130.0,`
			`"Y": 232.0,`
			`"StackOffset": {`
			`"X": 0.0,`
			`"Y": 0.0`
			`}`
			`},`
			`{`
Manually reorder objects in expected mapping The test added in 64baa4d01ae7bb9a2659a83c3e3238d2fbb07ef2 was previously failing despite applying a fix. This was caused by the fact that in stable, the last `sliderScoreTimingPoint` (i.e. the `LegacyLastTick` is pulled back by 36ms, but the list of all of them is not re-sorted afterwards, causing objects to be exported in non-chronological order to the resultant conversion mapping. lazer correctly sorts the objects, causing a false positive. 2023-09-15 18:07:59 +08:00			`"StartTime": 7817.0,`
			`"EndTime": 7817.0,`
			`"X": 30.9946651,`
			`"Y": 208.5157,`
Add test coverage of failing slider tick generation edge case 2023-09-07 17:20:07 +08:00			`"StackOffset": {`
			`"X": 0.0,`
			`"Y": 0.0`
			`}`
			`},`
			`{`
Manually reorder objects in expected mapping The test added in 64baa4d01ae7bb9a2659a83c3e3238d2fbb07ef2 was previously failing despite applying a fix. This was caused by the fact that in stable, the last `sliderScoreTimingPoint` (i.e. the `LegacyLastTick` is pulled back by 36ms, but the list of all of them is not re-sorted afterwards, causing objects to be exported in non-chronological order to the resultant conversion mapping. lazer correctly sorts the objects, causing a false positive. 2023-09-15 18:07:59 +08:00			`"StartTime": 7843.0,`
			`"EndTime": 7843.0,`
			`"X": 33.7820168,`
			`"Y": 208.9957,`
Add test coverage of failing slider tick generation edge case 2023-09-07 17:20:07 +08:00			`"StackOffset": {`
			`"X": 0.0,`
			`"Y": 0.0`
			`}`
			`}`
			`]`
			`}`
			`]`
			`}`