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
Kinda 2 issues I've seen, I think there are some improvements we can make to have the autocomplete powers of a Jupyter notebook.
There are some other issues but I saw on Discord there's some work on a native vscode plugin so I wonder what's the best way forward. Thanks!
Doesn't work all the time
This is likely due to frontend/src/core/codemirror/completion/Autocompleter.ts
did you notice any issues when removing validFor: /^\w*$/
yes, it's a little hard to debug, but I am finding some (like plotly commands) not autocompleting. Let me investigate, I'm not sure if it's because of this / a different bug.
What exactly are you experiencing here
I am expecting the docstring to show up as soon as I enter . like this:
I see the backend is returning empty completion docstrings when the number of options are too large, due to the docstrings_limit. This is likely why some libs like pandas / plotly have poor completions because the number of options can be very large.
Describe the bug
Kinda 2 issues I've seen, I think there are some improvements we can make to have the autocomplete powers of a Jupyter notebook.
There are some other issues but I saw on Discord there's some work on a native vscode plugin so I wonder what's the best way forward. Thanks!
This is likely due to
frontend/src/core/codemirror/completion/Autocompleter.ts
commenting out the validFor will give proper autocomplete.
This is due to docstrings_limit at
marimo/_runtime/complete.py#L316
Similar issue: #2080
Environment
Code to reproduce
No response
The text was updated successfully, but these errors were encountered: