Skip to content

feat: enable type checking for query selectors #2561

feat: enable type checking for query selectors

feat: enable type checking for query selectors #2561

Triggered via pull request October 11, 2024 19:42
Status Failure
Total duration 4m 44s
Artifacts

checks.yaml

on: pull_request
Matrix: preflight
Matrix: build
Matrix: unit-tests
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 10 warnings
typecheck: packages/signaldb/src/SyncManager/index.ts#L427
Argument of type '{ collectionName: string; }' is not assignable to parameter of type 'Selector<Snapshot<ItemType, any>>'.
typecheck: packages/signaldb/src/SyncManager/index.ts#L451
Object literal may only specify known properties, and 'id' does not exist in type 'Selector<ItemType>'.
typecheck: packages/signaldb/src/SyncManager/index.ts#L453
Object literal may only specify known properties, and 'id' does not exist in type 'Selector<ItemType>'.
typecheck: packages/signaldb/src/SyncManager/index.ts#L465
Object literal may only specify known properties, and 'id' does not exist in type 'Selector<ItemType>'.
typecheck: packages/signaldb/src/SyncManager/index.ts#L470
Argument of type 'Record<string, any>' is not assignable to parameter of type 'Selector<ItemType>'.
typecheck: packages/signaldb/src/SyncManager/index.ts#L479
Argument of type 'Record<string, any>' is not assignable to parameter of type 'Selector<ItemType>'.
typecheck: packages/signaldb/src/SyncManager/index.ts#L484
Argument of type '{ collectionName: string; time: { $lte: number; }; }' is not assignable to parameter of type 'Selector<Snapshot<ItemType, any>>'.
typecheck: packages/signaldb/src/utils/getMatchingKeys.ts#L9
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'FlatSelector<T>'.
typecheck: packages/signaldb/src/utils/getMatchingKeys.ts#L10
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'FlatSelector<T>'.
typecheck: packages/signaldb/src/utils/getMatchingKeys.ts#L11
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'FlatSelector<T>'.
build-docs
Process completed with exit code 3.
linting: examples/appwrite/next.config.js#L1
'@type' is redundant when using a type system
linting: examples/appwrite/next.config.js#L11
Missing JSDoc comment
linting: examples/appwrite/src/app/layout.tsx#L12
Missing JSDoc comment
linting: examples/appwrite/src/app/page.tsx#L7
Missing JSDoc comment
linting: examples/appwrite/src/containers/App/List.tsx#L4
Missing JSDoc comment
linting: examples/appwrite/src/containers/App/index.tsx#L5
Missing JSDoc comment
linting: examples/firebase/next.config.js#L1
'@type' is redundant when using a type system
linting: examples/firebase/next.config.js#L11
Missing JSDoc comment
linting: examples/firebase/src/app/layout.tsx#L12
Missing JSDoc comment
linting: examples/firebase/src/app/page.tsx#L7
Missing JSDoc comment