@cfleming what about using this? https://github.com/google/closure-compiler/tree/master/externs

@isak Oh, good find, thanks - that looks great

I’ll check the TypeScript ones, there’s potential I might be able to use the types if present. Looks like Closure uses jsdoc types though.

@cfleming any chance you could comment on https://github.com/cursive-ide/cursive/issues/711?

@dm3 Sure - so yes, Cursive understands Potemkin. There’s a hack you can use if the import-vars there works like Potemkin’s.

Cursive contains functionality to treat some forms in the same way as some existing form: https://cursive-ide.com/userguide/macros.html

Currently that has a hard-coded list of forms that you can resolve as, but under the hood it can be anything.

Which I’ll probably expose shortly.

hm, I’m still confused - do I have to do anything special to make Cursive recognize imported vars the same way it does the original ones?

In the meantime, you can hack your resolve config file as discovered by @favila here: https://github.com/cursive-ide/cursive/issues/1440#issuecomment-232776904

yeah, I don’t use Cursive myself - it’s people complaining about my library

If you modify the config file to treat clojure.java-time/import-vars (or whatever the var is) as potemkin/import-vars (or whatever that one is, I don’t have the code right here)...

Ah, I see

so potemkin/import-vars is hardcoded somewhere in Cursive, is that right?

Yes

In an extensible way, but yes

Could you create a new issue for that so it’s not mixed with the intern issue, and put the full clojure.java-time var in there, and I’ll add that?

@dm3 It’s just a copy of the Potemkin one, right?

yes

hm

Internally this is all based around an extension api, which I will open up at some point - then you’d just be able to make a fairly trivial PR to a public repo, and everyone would get that support.

Right now, I have to add it.

yeah, I see how that would work 🙂

ok, I’ll create the issue for now