Today textDocument/codeAction manages 2 things:

1. the position where code action can be executed
2. the execution of code action which computes the text edits.

I find it's shame to compute text edits 2) each time editor text changed although user could not execute it. More computing of text edits could be cost with some languages.

A proposal is to provide a new service called codeAction/resolve like LSP provides with codeLens/resolve and completionItem/resolve

In other words:

• textDocument/codeAction creates code actions with a given position and text edits (resolved) or not (not resolved)
• in case of code action is not resolved, codeAction/resolve is called to compute the text edits.

What do you think about this idea?