Yeah the report only really clogs up the console. But yeah sure a non-inline conditional is easier to read. I think we should keep the values as close as possible to the prod values though, so if one catches we see it in dev

remove inline conditional

Yeah I agree, added

increase breakpoints

Yes good call, no need to use it on the [slug] pages

revert comment

dont use the sort function uneccesarially

For sure Im not opposed to adding the sideshift widget

changing polling interval to 10

add comment for supress hydrationprop

remove unneeded condition

add more robust unit test

For next time could move the version number to a variable so you only have to change it in one place

@bot preview e.cash

And as far as that other test change in getScoreCardData, I added it here because the sort change was causing that test to fail as it was

Okay added, I couldnt think of a better place to put the scoreThreshold than at the top of scores.js, but open to suggestions

edit comments, add scorethreshold as a parameter and update tests

change classname, add comment