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
Currently, it seems like you can only provide context to errors.
Would be great if you could validate based not only on the class itself, but also additional context parameters provided during runtime.
You can technically achieve this by just wrapping all the context parameters into their own class, but this gets unmanageable quickly.
The text was updated successfully, but these errors were encountered:
In general the philosophy of Kotlin is that you should just create a new data class for specific data, see for example this KEEP. That would almost always be the best solution here i.m.o.
Specifically
this gets unmanageable quickly.
Can you give an example of where your proposed API would be significantly more manageable than creating a new data class for the purpose?
Currently, it seems like you can only provide context to errors.
Would be great if you could validate based not only on the class itself, but also additional context parameters provided during runtime.
You can technically achieve this by just wrapping all the context parameters into their own class, but this gets unmanageable quickly.
The text was updated successfully, but these errors were encountered: