and nullable should as uncommon as possible, maybe...
# codingconventions
n
and nullable should as uncommon as possible, maybe at conversion layers (json -> kotlin, java -> kotlin, …) but inside the kotlin code there should be no real need for nullable values. if it is necessary that’s not a common case from my point of view.