-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scala.JS: Cannot call lookupMethod(init___sc_Seq) on non Scala class sjs_js_Function #78
Comments
Could you make the bug report be minimized and reproducible? |
Yes - as described - in Stackoverflow. I created a branch: https://github.com/pme123/scala-adapters/tree/binding-issue-78 Master branch with a 'shorter' name works. |
Maybe it's reproducible, but still far from minimized. It would be easier to find the cause if it is minimized. |
Also adding a |
As it works now for me (Using shorter class name) - it is not so high in the priority list anymore. If I get some time I will try to minimize it. |
@sjrd How do you think? |
The relevant output from |
I tried to minimize the project - without success - a basic project with a case class that has a long name was not failing. Then I did what @sjrd suggested. These created huge logs that I added to a gist: https://gist.github.com/pme123/aadcc0fd101f6f7cf81e62f6f43d4fa1
The long class is called: |
I think the relevant code and logs are:
|
@pme123 The |
As described in the Stackoverflow question:
It doesn't matter what is in the onload function. I tried |
Interesting... |
I ran in a strange behavior, that I describe here:
https://stackoverflow.com/questions/50269126/scala-js-cannot-call-lookupmethodinit-sc-seq-on-non-scala-class-sjs-js-func
According to the comment of the creator of Scala.js that might be a bug in Binding.scala
The text was updated successfully, but these errors were encountered: