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
There are a few places in the code base where we currently throw exceptions that we might be able to convert to nullable return values or Kotlin's Result type instead, for example, in the SubmissionConverter.
We should do a pass to see if there are any cases in which we're overusing exceptions, or not using exceptions for cases that really are exceptional.
Once case where this might be used is in converter logic; converters could return Result rather than an exception so that there are compile-checks to ensure coroutines and Flows handle them correctly. See also google/ground-platform#931.
There are a few places in the code base where we currently throw exceptions that we might be able to convert to nullable return values or Kotlin's
Result
type instead, for example, in the SubmissionConverter.We should do a pass to see if there are any cases in which we're overusing exceptions, or not using exceptions for cases that really are exceptional.
See #2214 (comment) for additional context.
The text was updated successfully, but these errors were encountered: