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, the project uses unwrap() extensively, including within test code. While unwrap() is often used in tests for simplicity, it's not ideal as it causes panics when the value is None or Err.
We would like to eliminate the use of unwrap() and replace it with expect() in the test code to provide more helpful error messages in case of failure. Additionally, unwrap() should be removed from the core codebase to avoid unnecessary panics, improving the robustness of the application.
The goal is to:
In tests: Replace unwrap() with expect() to ensure clear error messages in case of failure.
In the codebase: Avoid using unwrap() and handle errors more gracefully, using proper error handling strategies where appropriate.
The text was updated successfully, but these errors were encountered:
Currently, the project uses
unwrap()
extensively, including within test code. Whileunwrap()
is often used in tests for simplicity, it's not ideal as it causes panics when the value isNone
orErr
.We would like to eliminate the use of
unwrap()
and replace it withexpect()
in the test code to provide more helpful error messages in case of failure. Additionally,unwrap()
should be removed from the core codebase to avoid unnecessary panics, improving the robustness of the application.The goal is to:
unwrap()
withexpect()
to ensure clear error messages in case of failure.unwrap()
and handle errors more gracefully, using proper error handling strategies where appropriate.The text was updated successfully, but these errors were encountered: