You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm testing with react-ace and python-lsp-server and got several exceptions in fromSignatureHelp (signatureIndex ==0, el == []).
However, upon further debugging it seems the trigger was the react-ace component being updated with a different value than the initial value (this also caused the lsp server to lose sync with the document).
Fixing the react-ace initialisation fixed the issue, but it seems ace-linters is not guarded against this scenario - is there a way to guard against it?
The text was updated successfully, but these errors were encountered:
Hi, I'm testing with react-ace and python-lsp-server and got several exceptions in
fromSignatureHelp(signatureIndex ==0,el == []).However, upon further debugging it seems the trigger was the react-ace component being updated with a different value than the initial value (this also caused the lsp server to lose sync with the document).
Fixing the react-ace initialisation fixed the issue, but it seems ace-linters is not guarded against this scenario - is there a way to guard against it?
The text was updated successfully, but these errors were encountered: