We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Setting options.enabled to false should override everything. For example:
options.enabled
false
Using useTransactions hook like this:
const transactions = useTransactions({ config: { params: { transactionID: search } }, options: { enabled: isTxId }, });
Should keep options.enabled in the useCustomInfiniteQuery hook.
useCustomInfiniteQuery
This code strips away the options.enabled completely.
const response = useCustomInfiniteQuery({ keys, config, options: { ...options, enabled: !!(client.socket || client.http) }, });
Which results in the search dropdown always being open
const isEnabled = options?.enabled !== false && !!(client.socket || client.http); const response = useCustomInfiniteQuery({ keys, config, options: { ...options, enabled: isEnabled }, });
The text was updated successfully, but these errors were encountered:
oskarleonard
No branches or pull requests
Expected behavior
Setting
options.enabled
tofalse
should override everything. For example:Using useTransactions hook like this:
Should keep
options.enabled
in theuseCustomInfiniteQuery
hook.Actual behavior
This code strips away the
options.enabled
completely.Which results in the search dropdown always being open

Suggested fix
The text was updated successfully, but these errors were encountered: