Pokey Rule
Pokey Rule
That's a good question. There are tradeoffs to putting in in either place. The advantage of extension-side is that it's easier to push updates and we have a lot more...
we only run legacy tests on linux anyway, so maybe we should just use `v0.10.0` as legacy?
Tried to run them in https://github.com/cursorless-dev/cursorless/pull/2256/commits/d9ce94c1afeff537fc24ee90c2091937e5b8d5c7; if that doesn't work I'll bail. Just figured I'd try to see if it were easy
Yep seems to work fine! I know 0.10.0 isn't very old, but I'm happy to just call that legacy for now. But I'll defer to the neovim folks to decide...
A package is the way to go, but I'd recommend starting from a clean checkout of `main` and then proceeding as follows: 1. Run the steps in the [docs for...
ok no worries; looks like you managed to remove all the unnecessary nx stuff so that's fine 👍. I'd move all the `lib/` stuff up to `src/` dir tho; that...
Oh interesting. I wonder why we do that there. Probably same reason tbh; was migrated from the old nx semi-mono-repo and never changed
> I've been working on mirroring the format of the `cheatsheet` for a `componentsheet`, I currently am getting stuck at module/types import from `@cursorless/test-case-component` but I think it's because I...
fwiw https://github.com/cursorless-dev/cursorless/pull/2286 now merged so hot reload should work once you do a git merge