-
-
Notifications
You must be signed in to change notification settings - Fork 84
Talon side spoken form tests #1637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just left a couple very quick comments
packages/cursorless-engine/src/core/commandVersionUpgrades/canonicalizeSpokenFormTestCommand.ts
Outdated
Show resolved
Hide resolved
7c4814f
to
d4c46bc
Compare
b811a27
to
996299a
Compare
f0092fa
to
ef56dae
Compare
Worth running through the checkboxes in these two issues to see if you've addressed everything. If not, I'm not saying you should do it in this PR, but we should prob not close those issues: |
Also you'll want to make a new branch pointing to what the base should be for this PR; I did a hard reset on the generateSpokenForms branch to make it easier to do some surgery. Then when that's merged you can cherry pick this stuff |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok this looks good to me, but for some reason is still failing for me locally, so we'll need to debug. Also worth having a look at the changes I made
The changes just looks fine. I just discover that after Talon has restarted some of the tests are failing for me as well. Touching a single Talon user file fixes this for some reason. |
oh haha you're right! |
Its the Cursorless simple actions list that don't get updated to default unless you touch a file. I will investigate further |
- Fixes #449 - Fixes #1675 ## Potential manual tests to add For these, just bake payload and spoken form into `const`s in the test itself - [x] "slice past" - [x] "two tokens forward" - [x] "one token" - [x] "take inside pair" ## Checklist - [x] Handle if Talon was in sleep mode initially - [x] Add deprecation warning if user says "to after"? I believe we support this today, and some users are still saying that, as indicated by slack questions from the past month. We could probably have this as an alternate spoken form for "after" and show a warning if they use it - [x] Stop using `generateSpokenForms` to check whether to run a test; instead read `spokenFormError` field on recorded test - [x] How do we actually want to launch this? Launch config in vscode and then? - [x] Add notifications when test start and stop - [x] I have added [tests](https://www.cursorless.org/docs/contributing/test-case-recorder/) - [/] I have updated the [cheatsheet](https://github.com/cursorless-dev/cursorless/tree/main/cursorless-talon/src/cheatsheet) - [/] I have updated the [docs](https://github.com/cursorless-dev/cursorless/tree/main/docs) - [x] I have not broken the cheatsheet --------- Co-authored-by: Pokey Rule <[email protected]> Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
Depends on #1637 - Fixes #725 - Partially addresses #1440 - Fixes #1319 ## Checklist - [/] I have added [tests](https://www.cursorless.org/docs/contributing/test-case-recorder/) - [x] I have updated the [docs](https://github.com/cursorless-dev/cursorless/tree/main/docs) and [cheatsheet](https://github.com/cursorless-dev/cursorless/tree/main/cursorless-talon/src/cheatsheet) - [x] Update cheatsheet spoken form defaults - [x] Manually test the various snippet terms - [x] Manually test the snippet apis - [ ] I have not broken the cheatsheet --------- Co-authored-by: Pokey Rule <[email protected]> Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
Depends on cursorless-dev/cursorless#1637 - Fixes #725 - Partially addresses #1440 - Fixes #1319 ## Checklist - [/] I have added [tests](https://www.cursorless.org/docs/contributing/test-case-recorder/) - [x] I have updated the [docs](https://github.com/cursorless-dev/cursorless/tree/main/docs) and [cheatsheet](https://github.com/cursorless-dev/cursorless/tree/main/cursorless-talon/src/cheatsheet) - [x] Update cheatsheet spoken form defaults - [x] Manually test the various snippet terms - [x] Manually test the snippet apis - [ ] I have not broken the cheatsheet --------- Co-authored-by: Pokey Rule <[email protected]> Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
Depends on #1637 - Fixes #725 - Partially addresses #1440 - Fixes #1319 ## Checklist - [/] I have added [tests](https://www.cursorless.org/docs/contributing/test-case-recorder/) - [x] I have updated the [docs](https://github.com/cursorless-dev/cursorless/tree/main/docs) and [cheatsheet](https://github.com/cursorless-dev/cursorless/tree/main/cursorless-talon/src/cheatsheet) - [x] Update cheatsheet spoken form defaults - [x] Manually test the various snippet terms - [x] Manually test the snippet apis - [ ] I have not broken the cheatsheet --------- Co-authored-by: Pokey Rule <[email protected]> Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
- Fixes cursorless-dev#449 - Fixes cursorless-dev#1675 ## Potential manual tests to add For these, just bake payload and spoken form into `const`s in the test itself - [x] "slice past" - [x] "two tokens forward" - [x] "one token" - [x] "take inside pair" ## Checklist - [x] Handle if Talon was in sleep mode initially - [x] Add deprecation warning if user says "to after"? I believe we support this today, and some users are still saying that, as indicated by slack questions from the past month. We could probably have this as an alternate spoken form for "after" and show a warning if they use it - [x] Stop using `generateSpokenForms` to check whether to run a test; instead read `spokenFormError` field on recorded test - [x] How do we actually want to launch this? Launch config in vscode and then? - [x] Add notifications when test start and stop - [x] I have added [tests](https://www.cursorless.org/docs/contributing/test-case-recorder/) - [/] I have updated the [cheatsheet](https://github.com/cursorless-dev/cursorless/tree/main/cursorless-talon/src/cheatsheet) - [/] I have updated the [docs](https://github.com/cursorless-dev/cursorless/tree/main/docs) - [x] I have not broken the cheatsheet --------- Co-authored-by: Pokey Rule <[email protected]> Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
Potential manual tests to add
For these, just bake payload and spoken form into
const
s in the test itselfChecklist
generateSpokenForms
to check whether to run a test; instead readspokenFormError
field on recorded test