You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
typeCallConfig is generating the wrong type when storeResult: false, example:
withCalls(()=>({loadProductDetail: typedCallConfig({call: ({ id }: {id: string})=>inject(ProductService).getProductDetail(id),mapPipe: 'switchMap',storeResult: false,}),checkout: ()=>inject(OrderService).checkout(),})),
The resulting store will still have loadProductDetailResult, even though it will not be populated when the response is received
Also, if storeResult: false is present, it should not allow defining a resultProp.
Workaround: not using typeCallConding , passing the object directly with storeResult: false correctly removes the type, but has the usual problems of not using the typedCallConfig, like loosing the types in callbacks like onSuccess
The text was updated successfully, but these errors were encountered:
typeCallConfig is generating the wrong type when storeResult: false, example:
The resulting store will still have loadProductDetailResult, even though it will not be populated when the response is received
Also, if storeResult: false is present, it should not allow defining a resultProp.
Workaround: not using typeCallConding , passing the object directly with storeResult: false correctly removes the type, but has the usual problems of not using the typedCallConfig, like loosing the types in callbacks like onSuccess
The text was updated successfully, but these errors were encountered: