Skip to content

Better context and discoverability for custom operations #9534

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

Open
cartermp opened this issue Jun 23, 2020 · 0 comments
Open

Better context and discoverability for custom operations #9534

cartermp opened this issue Jun 23, 2020 · 0 comments
Labels
Milestone

Comments

@cartermp
Copy link
Contributor

See here for more context: fsharp/fslang-suggestions#880

Essentially, when inside of a CE it would be nice if completion had a better understanding of the custom operations that are valid for the CE. From Saturn library:

let endpointPipe = pipeline {
    plug head
    plug requestId
}

If I type p, a valid custom operation is at the top of the completion list:

image

But if I type a, I get a full completion list, the vast majority of which will never actually compile:

image

This isn't inherently a problem, but the lack of context about the code we're in can show up pretty quickly.

Additionally, it'd be nice if there was a way to essentially query for a list of available custom operations for a given CE. This is a part of a greater set of problems around context with completions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: New
Development

No branches or pull requests

2 participants