2 replies
Hey guys I have a problem while building project with ngrx/effects :
installed : "@ngrx/effects": "11.1.1", does anybody know what is going on ?
Error: node_modules/@ngrx/effects/src/concat_latest_from.d.ts:2:145 - error TS2574: A rest element type must be an array type.
export declare function concatLatestFrom<T extends Observable<unknown>[], V>(observablesFactory: (value: V) => [...T]): OperatorFunction<V, [V, ...{
[i in keyof T]: ObservedValueOf<T[i]>;
}]>;installed : "@ngrx/effects": "11.1.1", does anybody know what is going on ?
still active community here? question about entityAdapter,
it seems like deeper object key data is overwritten completely instead of concat, what i would expect.
if this is my entity:
'93dd0fd6-fd8c-4c70-a213-cb76d1ef6eda': {
guid: '93dd0fd6-fd8c-4c70-a213-cb76d1ef6eda',
languageSettings: {
DE: {
slug: 'velows',
},
EN: {
slug: 'velows',
},
FR: {
slug: 'velows',
},
NL: {
slug: 'veluwe',
},
},
},and i update the object with a specific language for content like
```
'93dd0fd6-fd8c-4c70-a213-cb76d1ef6eda': {
guid: '93dd0fd6-fd8c-4c70-a213-cb76d1ef6eda',
languageSettings: {
EN: {
slug: 'velows',
title: 'Testing EN',
content: 'Test',
},
},
},How do i concat with the entityAdapter?
https://stackoverflow.com/questions/66592750/ngrx-unrelated-select-firing-when-updates-another-slice-of-state
^ basically this exact thing is happening to me.
Unrelated selectors are firing when I change a different slice of the app state...
^ basically this exact thing is happening to me.
Unrelated selectors are firing when I change a different slice of the app state...
I don't see anywhere that I can put "distinctUntilChanged" with the "new" ngrx syntax... 🤔
export const selectConnectedAccount = (state: AppState) => state.login ngOnInit() {
this.store
.pipe(
map(state => {
console.log('mapping state header: ', state)
return selectConnectedAccount(state);
}),
filter(val => val !== undefined),
filter((val: any) => val.currentAccount !== undefined),
// distinctUntilChanged
)
.subscribe(
state => {
if (state.currentAccount) {
console.log('got new connected address: ', state)
this.connectedAddress = state.currentAccount;
// Uncommenting below line causes infinite loop of ngrx actions firing...
// this.store.dispatch(loadHydrants({ account: this.connectedAddress }))
console.log('got address, dispatching call for hydrants... ', this.connectedAddress)
}
else
console.log('got empty state: ', state)
}
)
}export interface AppState {
login: any;
hydrants: any;
}
i'm using angular 12 + ngrx 12.2 + router-store. i have a ItemListComponent that shows a list of items and ItemDetailsComponent that shows details about one item. if i go to the list component and get the list of all items and then from there router.navigate to the Details component e.g. /itemDetails/1 everything works fine using <div *ngIf="item$ | async as item" however, if i navigate directly to the /itemDetails/1 the item details don't show up. in my facade, i have
selectedItems$ = this.store
.pipe(select(ItemsSelectors.getSelected))
.pipe(
tap(project => {
if (!project) {
this.loadAllItems();
}
}),
filter(project => {
console.log('item: ', item);
return item !== undefined;
})
);i can see it logging the empty item before it pulls the list and the item with data after
@syndesis it has been quite a while I used router-store, but I could remember that there seemed to be a race condition between the declaration of the effects, and the router events. Basically I was missing actions because the ROUTER events were not caught by the effects on navigating directly to the components as the effects were not loaded at that time. it was about 3 or 4 years ago though, this might have changed, but I would look into this if I were you
i don't know why that's different from an outer div on the original component, though
There exists plenty of documentation to migrate the selector itself, but nothing clear. If anyone has a path I'm quite happy to throw up a docfix PR :)
if you need to do something customized you can still use all of those things, but you shouldn't need to in most cases
It isn't hard...angular university has a great course on it..I would recommend taking that
basically if you have an entity names car, if you make a getAll call, the API would look for an endpoint named cars
if you are using getById() it would look for an endpoint named car
etc
and it basicaly just works like magic
@BertrandMarechal @CodeLiftSleep this guy explain very well how it works:
https://www.youtube.com/watch?v=TenetyDn4XM&ab_channel=ApplicableProgramming
https://www.youtube.com/watch?v=TenetyDn4XM&ab_channel=ApplicableProgramming
consider ngrx/data can you have different slice for each enitity? if you need lets say slice1 state into slice2, can you access it?
as i understood ngrx data does not neet reducer, effects etc in order to store data
every time we subscribe to an selector, the current value is emited inmediately after subscription, is there a way to subscribe to a selector but only get the subsequent emitions after the subscription not the current value?
I need to subscribe to a selector observable but only get the values AFTER the subscription. Thanks
I need to subscribe to a selector observable but only get the values AFTER the subscription. Thanks
