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
I just stumble across the following in current master branch:
useGetMatchingReferenceSelector filter prop is defined but not being used inside the hook.
useGetMatchingReferenceSelector
filter
I believe it could affect the initial value of useReferenceInputController filter prop.
useReferenceInputController
const useGetMatchingReferenceSelector = ({ referenceSource, filter, // <-- Defined, but not used reference, resource, source, id, }) => { const getMatchingReferences = useCallback( state => { const referenceResource = getReferenceResource(state, { reference, }); const possibleValues = getPossibleReferenceValues(state, { referenceSource, resource, source, }); return getPossibleReferences(referenceResource, possibleValues, [ id, ]); }, [referenceSource, reference, resource, source, id] ); return useSelector(getMatchingReferences); };
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
I just stumble across the following in current master branch:
useGetMatchingReferenceSelector
filter
prop is defined but not being used inside the hook.I believe it could affect the initial value of
useReferenceInputController
filter
prop.The text was updated successfully, but these errors were encountered: