What’s funny, is that we already do have autocomplete for it because property dot-autocomplete works in our tooling. What we don’t have is autocomplete for generic methods, which is Julia’s idiomatic style.
In other words, we are being encouraged by our tools to betray Julian style in favor of OO style. Thankfully the community hasn’t done that, so there is instead, broadly speaking, poor method discoverability. 
And these are some of the better-documented language features; some of the other packages are always under such rapid development, that their documentation is in a continuously-mildly-broken state and you have to experiment to find what you’re after. Some have set up RSS feeds so users could keep abreast of updates. And some of the most sophisticated packages use args...; kwargs... for their arguments so you can’t even figure out which arguments are valid from their method signatures 
We discussed some ideas for how method autocomplete could work here, in the context of how a chaining syntax could help the issue; @Palli linked the latest chaining syntax proposal.