nope

# getting-started

[cookiecookiecookie]

nope

[Adam Powell]

Hi! This slack is a big place so usually it's considered polite here to keep discussion on one topic as replies in a single thread rather than posting repeatedly to a channel.

[Adam Powell]

Why do you want this? Usually in Python you would use dir() in the repl to learn about an API surface, it's not terribly common to do it in "real" code

[Adam Powell]

In kotlin you would normally use the IDE's code navigation features instead to browse through the source and API docs for types you're using, e.g. ctrl+click on a type name to jump to its declaration, or hover over something while holding ctrl to see a popup about it

[Adam Powell]

Or if your cursor is on the name of something press Ctrl+Q for "quick documentation" of whatever that thing is

[Adam Powell]

it'll tell you its type and more info about it that you can then drill further into if you like

[cookiecookiecookie]

hey adam

[cookiecookiecookie]

thanks for getting back to me

[cookiecookiecookie]

normally i would be doing that in an ide as yo mentioned however i’ve been using Kotlin in Jupyter

[cookiecookiecookie]

and it is like python as in a repl interface

[cookiecookiecookie]

so i was just wondering how to get around it such that i quickly find methods and such without having to go look it up

[cookiecookiecookie]

or use an ide

[cookiecookiecookie]

bit of a hack

[cookiecookiecookie]

but yeah 😄

[Adam Powell]

Ah, then yeah that will get you signatures but no doc strings and such