:android-wave: If I create an @optics for a model that has a `someField: String?` , in order to set/...

# arrow

[Rafal]

👋 If I create an @optics for a model that has a someField: String? , in order to set/modify it I have both someField and nullableSomeField lenses. This won't be a case in Arrow 2.0? If not, why are both lenses are created instead of only the nullable one?

[Alejandro Serrano.Mena]

right now @optics give you a single someField: Optional<T, String>, but with Arrow 2.0 you'll get someField: Lens<T, String?>

[Alejandro Serrano.Mena]

the difference is that with the 1.x behavior you cannot change a null value into a non-null one and viceversa, but with 2.x behavior you can

[Rafal]

hmm weird, I can see only that in the generated code, using Arrow 1.2.4