Stefan Buck

Thanks for your quick reply. Yeah I thought about scripting on top of `comby` as well. However, it feels like there is just one tiny piece missing (at least for...

I think a Comby VSCode extension is crucial to get much more adoption. Also it ease the experience for existing comby users as well. I use https://comby.live quite a lot,...

You can use the new [GlobalStorage](https://github.com/yeoman/generator/blob/8e2ef622524403e89c538e19299913498265c246/lib/base.js#L160) to store the location for the next time :wink:

I'm sorry for the very late reply. Somehow this message slipped through my inbox. I don't see any issue with adding such a user.

> Actually might want to do this request with only Chrome versions and then we can tell people if they want a Nodejs version they need to find the nearest...

@SimenB are you aware of any existing Problem Matcher for Jest? The Jest output isn't really suitable for parsing using a RegExp or at least not that simple. I was...

I proposed a similar idea using a json output and `xpath` https://github.com/actions/toolkit/issues/260. Internal we use [Danger.js](https://danger.systems/js/) to attach the jest output as a PR comment, but using a Problem Matcher...

> Problem matchers are for parsing console output and are run line by line. In you case you want a file and the runner won't when to process the file....

I tend to prefer a new reporter mainly because it doesn't involve GitHub roadmap prioritization 😉 I'll look into this and keep you updated.

I started working on this and the first issue I'm facing is the limitation to a single line for the message field https://github.com/actions/toolkit/issues/319. I guess there is not much we...