You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we create Java Beans in Scala 2 using @BeanProperty it will have 2 setters for each @BeanProperty val foo: Foo property:
defsetFoo(foo: Foo):Unitdeffoo_=(foo: Foo):Unit
Both of them will be called when setting up things in derived type class.
Find a reasonable way to avoid issues with this case e.g.
preferring only calling foo_= when both methods can be proven(?) to be generated by annotation
ditto but preferring setFoo
calling both of them BUT ensuring that pipe converting value to output type will be only called once (limiting side effects and computations in converter but ensuring that both fields are called)
using a flag to decide between behaviors above and selecting one of them as the default
The text was updated successfully, but these errors were encountered:
When we create Java Beans in Scala 2 using
@BeanProperty
it will have 2 setters for each@BeanProperty val foo: Foo
property:Both of them will be called when setting up things in derived type class.
Find a reasonable way to avoid issues with this case e.g.
foo_=
when both methods can be proven(?) to be generated by annotationsetFoo
The text was updated successfully, but these errors were encountered: