-
Notifications
You must be signed in to change notification settings - Fork 3
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
Document features (and add fancy gifs) #9
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.
First round of commands, this looks great overall !
from an expression to the parent `let`, the parent `module`, the | ||
parent `fun` and the parent `match` expression. It is also possible to | ||
navigate between pattern matching cases: | ||
|
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.
We should indicate the targets for pattern matching cases. Even better, could they appear as suggestions when calling the command ?
The custom request can also return all possible targets with the corresponding jump, that might be a better workflow ?
- Execute the command which wait for the CR answer
- Ask the user which of the available jumps she wants to perform.
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.
Oh yes, non giving a target will compute every available targets?
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.
Yes !
Co-authored-by: Ulysse <[email protected]>
No description provided.