Add the generate-examples library

[SimeonC]

Have issues with the selections not quite being generated and inserted correctly (recursive selections are kinda hard).

Current output of the buildDictionary script is being manually ported into https://codepen.io/SimeonC/pen/gOeBJLr

• partially addresses Create web page to represent test cases #866

[pokey]

Hi @SimeonC, just checking in on this one to see:

• What still needs to happen on this PR?
• Do you have any bandwidth to work on it, or should we take it over?

Thanks!

Fwiw I resolved merge conflicts so make sure to pull if you start hacking again 😊

[SimeonC]

Hi @pokey. Sorry for the radio silence, had a 3-month performance refactor that sapped all my mental energy and time. That's over and finished and I was hoping to get back and figure this out a bit more at some point.

For what's left, I think it's the following;

• type issues
• some bugs in the generation around creating selections
• moving in the CSS code from the codepen (and completing it for all the cases)
• define some kind of internal API so it can be called properly or something like that

I may not have any bandwidth until next year due to Christmas leave (unless I get some time next week). I definitely wanted to finish this - if you guys want to take it over and finish it to get it on the website I don't mind, I'm not so attached to it to block you guys from getting the features out you want.

[pokey]

Hi @SimeonC. No worries; just wanted to check in. We have other stuff to focus on at the moment, so wouldn't pick it up until next year anyway. Happy to leave it with you for the time being

[SimeonC]

I'm still alive!! 🤣 Finally found some time and realised that my old code was so bad that there was no way I wanted to figure out what was going on so I started again.
In the interim at work we have been looking through the "Clean Coder" so I've applied some of that - primarily using classes, smaller functions and TDD. Which should make this PR overall much better to review.

[pokey]

Nice! Will have a look. Fwiw we're about to be on a proper pnpm monorepo; expecting #1313 to be merged in next 48hrs

[SimeonC]

Oh, sorry - must have accidentally deleted the line that said that this still needs work - a couple more evenings when I get the chance. Mostly wanted to say I am still trying to find time to get this done and haven't just gone silent and ghosted you all.

[pokey]

ah ok cool lmk when you want me to take a look; i'm happy to give early feedback if helpful

[pokey]

Ok we're now a pnpm monorepo. The cursorless-nx subdir is gone. You'll want to put your package in the packages directory. See https://www.cursorless.org/docs/contributing/adding-a-new-package/

Also note that you can now import from the cursorless codebase, which should make your life easier

[pokey]

Re importing packages from the rest of Cursorless codebase, any package that doesn't have vscode in the name is fair game to import for your build pipeline. If you need to import one of the packages into browser runtime context, let me know; we are planning to abstract away references to node but haven't gotten there yet

[pokey]

@SimeonC lives! 😄

Good to see you hacking again. A lot has changed in this repo since you last merged up 😅. Maybe worth dropping into a meet-up to discuss?

Note that we now have a spoken form generator that you could just use, but not sure it's necessary anymore as all of the spoken forms in our test cases have now been canonicalised, so I think you could just use the spoken form from the test case

[SimeonC]

😆 Yea, I finally found some time. I've just been hacking away at the generation part and I can go figure out how to update everything to fit the updates.

[pokey]

Fwiw we've also started just upgrading text fixture command payloads on the fly if we need the latest, so you should be able to do that to have your code work on legacy test fixtures.