joyride

pez 2022-05-10T16:27:32.024579Z

Anyone savvy with shadow-cljs to figure out how we can ”bundle” the npm modules Joyride needs to be able to package it for https://vscode.dev? https://github.com/BetterThanTomorrow/joyride/discussions/48

seancorfield 2022-05-10T18:39:02.969499Z

I see issue #36 will no longer show the Joyride output channel when scripts are run, but it still shows the output channel by default at startup, yes? (I have 0.0.8 installed and sort of expected that not to appear at startup)

pez 2022-05-10T18:40:01.234819Z

You expected wrongly. 😀 I’ll get to this one.

👍🏻 1
Max 2022-05-10T19:49:40.463169Z

When dev’ing on joyride itself, is it expected that it throws a big error about vscode/workspace.rootPath being null when starting the extension in debug mode?

pez 2022-05-10T19:55:28.063509Z

Not seen it, but if the debug extension host window has not folder open, I guess this might happen. We do not handle that case yet. Is that what you have?

Max 2022-05-10T19:56:40.612099Z

Yeah, the debug extension host had no folder initially. I think adding one made it happy?

pez 2022-05-10T19:58:40.186099Z

Yes, with a folder open Joyride is happy. Please file an issue about this.

👍 1
Max 2022-05-10T20:02:58.981289Z

Filed: https://github.com/BetterThanTomorrow/joyride/issues/51

🙏 1
Max 2022-05-10T20:22:21.967979Z

Sorry, one more question: is there currently somewhere to put tests? I was going to add one for the pprint PR I’m finishing, but I couldn’t find any prior art

pez 2022-05-10T20:56:30.664799Z

Still on todo. We'll need to tease things apart so that we don't require vscode in the modules under test, or the shadow test runner will not be able to run them.

👍 1