fix: 🐛 use 'sift/lib' import to restore proper type inference #216
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates imports from
sifttosift/libto fix a typing issue caused by the default export of the sift package. The main sift entry point does not preserve the full type signature of its default export (createDefaultQueryTester), which results in incomplete or incorrect typings in consuming code.Problem
When importing from sift directly:
TypeScript fails to infer the correct type and raises the error:
This happens because the default re-export in the root entry point lacks proper type propagation.
Solution
This PR changes the import to:
This directly references the file that properly exports
createDefaultQueryTesterwith full type annotations, restoring correct type inference.