Closed gochev closed 1 year ago
Hi @gochev. It looks like your use-case involves a package class in the same file as the main class, right? That case appears to be broken. However, the general case of a package-private class with properties works as it should. I'll take a deeper dive into the former case. Thanks for reporting this!
I've verified the general case of a package-private class with properties works as it should. The only case that does not work is when the class is a top-level class that resides in another top-level class' file. Manifold generally ignores that case everywhere; it is not likely to get fixed. Sorry.
I suppose what should be done is to produce a compile error instead of causing an NPE. Expect that soon.
Fixed with release 2022.1.32
Describe the bug
if you just define your class as internal in the same package as main the @var will not work - the compile will fail, and if you run it with the intellij plugin you will get NPE.
To Reproduce
Expected behavior To work also for classes defined like this one.
Screenshots On maven compile On Run
Desktop (please complete the following information):
Additional context If I move this into a PUBLIC class like this it works
it is not because of the default package.. also tried to move the main and internal class into a package (instead of empty) its the same.
Still AMAZING work :) LOVE IT !