Help request

[kfxs]

So, here I am again.

Should I start trying to understand the parser....
Or is it something more useful to do?

[frostburn]

Did you check if the current version of https://github.com/xenharmonic-devs/sw-server works with your current changes in the open PR?

If it happens to work out of the box, we could consider merging and deploying to staging.

Once I have time to implement the inline stuff I'm going to make you review the grammar changes so getting familiar with https://github.com/peggyjs/peggy would be time well spent too.

[kfxs]

I had some free time today and was able to run sw-server locally. While using SW3 and clicking on Share scale Copy this scale's unique URL to clipboard the data of the box seems to be saved on the backend; since I used the URL from the clipboard on a new tab (and in a new browser)r, all the information regarding the symbols was there. I don't know if is magic or some changes where done at sw-server .

[frostburn]

Good to know. It's JSON so it makes sense that it just works if you wrote the serialization and deserialization code correctly. I'll investigate myself tomorrow.

[frostburn]

I can confirm that it works. Now we just need to figure out how to version this so that future staging releases of Scale Workshop 3 know to reject scales with an extra text box. I'd very much like the syntax to be inline. I also don't want to do any data migrations, but we should still let people play around with staff notation while we work on that.

Another can of worms is communicating to users not to use staging for serious work. I occasionally see non-plainsound URLs in #dank-scales-bruh on Discord.