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
As a developer I use the useSeek composable a lot in my project. Sometimes objects I search for do not exists – but that's ok and I want to handle it on my own. I don't need the warning in development and I don't want the warning in production.
Suggested solution
Do not log a warning in a production environment.
Alternative
Add an options prop to the useSeek composable to conditionally turn the warnings on and off, like so:
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
The text was updated successfully, but these errors were encountered:
lnvglr
changed the title
useSeek composables should not trigger a warning (in production) if no objects were found
useSeek composable functions should not trigger a warning (in production) if no objects were found
Sep 12, 2024
lnvglr
changed the title
useSeek composable functions should not trigger a warning (in production) if no objects were found
useSeek functions should not trigger a warning (in production) if no objects were found
Sep 12, 2024
Description
As a developer I use the useSeek composable a lot in my project. Sometimes objects I search for do not exists – but that's ok and I want to handle it on my own. I don't need the warning in development and I don't want the warning in production.
Suggested solution
Do not log a warning in a production environment.
Alternative
Add an options prop to the useSeek composable to conditionally turn the warnings on and off, like so:
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: