Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

useSeek functions should not trigger a warning (in production) if no objects were found #830

Open
4 tasks done
lnvglr opened this issue Sep 12, 2024 · 0 comments
Open
4 tasks done

Comments

@lnvglr
Copy link

lnvglr commented 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:

const { seekAll } = useSeek({ warning: process.env.NODE_ENV !== 'production')

Additional context

No response

Validations

@lnvglr 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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant