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
One of the strengths of Kotlin as a typed language is the discoverability of the API shape, which is more accessible than for dynamic languages.
However, that seems a bit broken in Jupyter where you don't get any help for parameters, but have to discover them yourself through documentation or samples.
Example with Dataframes:
The first argument to DataFrame.readCSV( is required and is one of 4 options. However, that is impossible to tell from the huge list of autocomplete options and you can only discover this through documentation.
If you do know the name of the parameter, you can get it to show up, e.g like this:
But that is hardly ideal.
Compare this to IntelliJ which shows it like this:
Which is much easier to digest and act upon.
This issue #17 does mention that the current autocomplete is a bit dumb, but it was also closed. So I thought I would open this issue to track improving the autocomplete.
The text was updated successfully, but these errors were encountered:
One of the strengths of Kotlin as a typed language is the discoverability of the API shape, which is more accessible than for dynamic languages.
However, that seems a bit broken in Jupyter where you don't get any help for parameters, but have to discover them yourself through documentation or samples.
Example with Dataframes:
The first argument to
DataFrame.readCSV(
is required and is one of 4 options. However, that is impossible to tell from the huge list of autocomplete options and you can only discover this through documentation.If you do know the name of the parameter, you can get it to show up, e.g like this:
But that is hardly ideal.
Compare this to IntelliJ which shows it like this:
Which is much easier to digest and act upon.
This issue #17 does mention that the current autocomplete is a bit dumb, but it was also closed. So I thought I would open this issue to track improving the autocomplete.
The text was updated successfully, but these errors were encountered: