Flavio Brasil
Flavio Brasil
> After loading of object from DB all @transient val fields are null. That's expected, since they are transient, they aren't persisted. > lazy val fields throw > java.lang.ClassCastException: java.lang.Boolean...
> But shouldn't they be reevaluated after select? No, unless it's lazy.
Just create a new test context[0], add a new test category[1] and run `sbt test`. There will be a prompt to select the categories you'd like to test. [0] https://github.com/fwbrasil/activate/blob/master/activate-test/src/test/scala/net/fwbrasil/activate/ActivateTestContext.scala...
@aardelean Could you send the complete stack trace?
Unfortunately, looks like there isn't a way of executing code after the execution. Shutdown hooks don't work with sbt run.
@frossi85 Could you investigate if there is a way of run arbitrary code during the sbt reload?
It is possible to implement, but I'm afraid I won't have time to work on it on the short/mid-term.
@claytonsilva Only immutable lists are supported, the mutable isn't supported. :) @odwrotnie Does the `AttributeValue` class have an attribute that has `T` as its type?
This is the expected behavior, since the validation is done in more than one phase. Is it affecting your application's behavior?
Yeah, there is space for optimizations for the invariants. Lets keep this issue open to review the invariant validation phases.