IDEA indexing

[Adam-Vandervorst]

IDEA does not give me code insights into Laminar.

My setup:
IDEA: 2021.2.3
Scala: 3.1.2-RC1-bin-20211124-1f48de1-NIGHTLY
SBT: 1.5.5
Dependencies: just "com.raquo" %%% "laminar" % "0.13.1"

Details:
import com.raquo.laminar.api.L.{*, given}
does work with fastLinkJS, but gives no insights beyond the api level.
import com.raquo.laminar.nodes.RootNode
does give me insights from a .tasty file.

I'd say sources of some sort are missing, or something is not loading.
Would love to try out Laminar and insights helps exploring the functions and signatures.

[yurique]

This is with scala3, right?
Last time I tried it, barely anything worked in IDEA with scala3 :'(

[raquo]

I have to agree. Scala 3 support is so broken / incomplete in IntelliJ, I'm still stuck with Scala 2.

For Laminar I'm using a very standard sbt-release config, I doubt that the problem is on Laminar's end. You can try asking in their gitter and/or filing it as a bug in jetbrains youtrack.

[Adam-Vandervorst]

Ha I have been using Scala 3 in IDEA for the past 7 months and it's running decently well now.
I don't think it's on Laminar's end, but maybe you had found a way around the particular issue occuring here.

Will definitely reach out, thanks!
Regarding my current Scala 3 project, am I correct in concluding it's not the right time to use Laminar?

[raquo]

Why not? I personally am waiting for IntellijJ to sort out their issues, but Laminar has supported Scala 3 natively for months now.

[Adam-Vandervorst]

That's why I'm asking -- good to hear, the project looks like a perfect fit.
I just tested import com.raquo.laminar.api.Laminar.{*, given} and that does given me code insights 🎉.
That leads me to believe the inspection doesn't carry through all (any?) information from val L: com.raquo.laminar.api.Laminar.type = ???.

[Adam-Vandervorst]

Hmm the code insights work but the compiler rejects it with

[error] 1 |import com.raquo.laminar.api.Laminar.{*, given}
[error]   |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[error]   |object Laminar cannot be accessed as a member of com.raquo.laminar.api.type from module class <empty>.

[Adam-Vandervorst]

code insights work

This is an overstatement, as it does highlighting and typing correctly, but it can't see the members.
Concretely

controlled(value <-- inp, onInput.mapToValue.filter(stateMachine.currentlyValid) --> inp)

recognizes the arguments for controlled and the signature for value and onInput, but does not see .mapToValue.
Maybe it doesn't see what's behind the .tasty definitions.

[raquo]

Any IntelliJ issues you run into with Scala 3 will surface easily with other Scala.js libraries too, or if not the same exact issue, then something else will pop up. At least that's been my experience.

[raquo]

Well, that's to be expected, you should import all that stuff either from `api` or from `api.L` as mentioned in the docs, not from `api.Laminar` – that object is private on purpose. You should look at errors given to you by the real Scala compiler, not by IntelliJ. Normally that wouldn't be an issue but since their Scala 3 support is not complete you have to account for that.

[Adam-Vandervorst]

That makes sense, just reporting it does have some insights into the types that way, over the api and api.L.

[raquo]

Btw try the new IntelliJ 2021.3 version, among the fixes in their changelog:

In addition, the TASTy reader can now parse package objects

Seems relevant.

…

--Nikita

On Wed., Dec. 1, 2021, 3:38 a.m. Adam V, ***@***.***> wrote: That makes sense, just reporting it does have some insights into the types that way, over the api and api.L. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#112 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAECBMBDM4GTMFTWYQVHMJTUOYCMNANCNFSM5JCHVXRA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[Adam-Vandervorst]

That improved something: L.{*, given} now provides the same insights as Laminar.{*, given}.
So still nothing for .mapToValue (or anything but the top level definitions), but that's a start!
Do you see a workaround for the .tasty files? I'm considering making it a submodule as this exposes the .scala files and building Laminar looks relatively straightforward.

[raquo]

Sadly I don't know much about Scala build tools and internals like tasty files