Muir Manders
Muir Manders
I don't really have good understanding of code lens use cases in general, but I might start with something like: 1. If active region, choose code lenses that start or...
> > There is lsp-avy-lens. > Is that good enough for you? That only shows lenses currently visible in the buffer, right? I want something that shows all the available...
> The non-visible lenses might not be resolved so showing all lenses in the file is not an option. I thought the code lens response includes all lenses for the...
Don't code actions and completion items have the same thing? We show lists of those before resolving them.
Ah, I didn't realize the lens names can require resolving. Thanks. Anyway, I still thing there should be a non-visual way to invoke lenses. If there is a code lens...
I'm not sure this would be safe behavior in general. Consider a case like: ```go func _(greatName int) int { badName := 123 greatName = badName - greatName // lots...
Also remember that rename applies to the entire module including files not open in your editor. If the user is in the middle of a big change with many modified...
What if we allow slaphappy renames but save off a patch of the changes to let the user "undo" if they want?
> Shouldn't the IDE already be saving a patch of the changes? Not if the files aren't open in the IDE. But that is another option - if the renames...
@stepancheg By GitHub jobs are you referring to CI jobs from ".github/workflows"? I just tested and CI jobs were started on a PR I created using "sl pr submit". Do...