@Js
class Example {
// WARNING: Type 'acme::JvmOnly' not available in Js
JvmOnly? test1() { null }
// WARNING: Type 'acme::JvmOnly' not available in Js
Void test2(JvmOnly jvm) { }
// No warning
Void test3(|JvmOnly| func) { }
// No warning
|JvmOnly|? test4() { null }
}
class JvmOnly {}
Generally, warnings are given for types not available in Javascript - but it doesn't seem work for func params.
andyWed 28 Oct 2015
Ticket promoted to #2488 and assigned to andy
HenryTue 19 Jan 2021
This issue has also affected me:
@Js
class Example {
JvmOnly[]? test
}
class JvmOnly {}
This also isn't generating a warning in the Example class regardless of whether the field test is used or not.
Regards,
matthewFri 22 Jan 2021
Ticket resolved in 1.0.76
I pushed a fix for this that will be in the next build. It should be fairly robust now in terms of finding usage of non-JS types.
SlimerDude Tue 27 Oct 2015
I noticed this the other day:
Generally, warnings are given for types not available in Javascript - but it doesn't seem work for func params.
andy Wed 28 Oct 2015
Ticket promoted to #2488 and assigned to andy
Henry Tue 19 Jan 2021
This issue has also affected me:
This also isn't generating a warning in the Example class regardless of whether the field test is used or not.
Regards,
matthew Fri 22 Jan 2021
Ticket resolved in 1.0.76
I pushed a fix for this that will be in the next build. It should be fairly robust now in terms of finding usage of non-JS types.