I wondered if anyone has created any "updater" scripts that would bring my code from class based/Type enum/switch based NgRX to the new create* syntax (yeah, I know it isn't really "new" any more but my company has just gotten around to upgrading from Ng7 to Ng11.)
So far, the best I've been able to come up with is a macro that uses Regular Expressions and search and replace. I was just hoping there was something smarter out there.
Hello! I'm trying to figure out how to test an selector (selectAll from and EntityAdapter) from a FeatureState. E.g.:
export const selectFeatureState = createFeatureSelector<EntityState<fromModel.ModelWithId>>('FeatureKey');
export const selectAll = createSelector(
selectFeatureState,
fromModel.entityAdapter.getSelectors().selectAll
)It normally seems to work but sometimes my tests are flaky:
const items: ModelWithId[] = [
{ id: 2 },
{ id: 1 },
] as any;
const entityState = createEntityAdapter<ModelWithId>().setAll(items, fromModel.initialState);
const featureState = { [fromSelector.featureKey]: entityState };
// Sometimes flaky
describe('selectAll', () => {
it('should return all cached items', () => {
expect(fromSelector.selectAll(featureState)).toEqual(items);
});
});I searched in quite a few resources, but I'm still unsure if the selector or the way I test or even something I don't consider could be wrong. Any hint would be helpful.
Hello team I am getting below TSLint issue.
Package is buiding fine and working fine.
Argument type () => Observable<TypedAction<"[WidgetInfo] init failed"> | ({data: IClientListResp} & TypedAction<"[Channels] get channels list success">)> is not assignable to parameter type () => (Observable<TypedAction<"[WidgetInfo] init failed"> | ({data: IClientListResp} & TypedAction<"[Channels] get channels list success">)> & ConditionallyDisallowActionCreator<DispatchType<EffectConfig>, Observable<TypedAction<"[WidgetInfo] init failed"> | ({data: IClientListResp} & TypedAction<"[Channels] get channels list success">)>>)here is my code,
getChannelsListSuccess$ = createEffect(() => this.actions$.pipe(
ofType(actions.getChannelListSuccess),
exhaustMap(({ data }) => {
let { channels, ...client } = data;
return [actions.setClient({ client: client as IClient }), actions.setChannels({ channels: channels })];
}),
catchError((err) => {
console.log(err);
return of(actions.initWidgetFailed());
})));I am using webstrome as editor
But in this case the open closed principle does not even apply: you don't extend the reducer.
And you have to be lucky that you can use a action multiple times (meaning extending the reducer). Sometimes it works, sometimes not.
If the store must access the actions from the component and the component must access the selectors of the store - seems like an impossible situation
We are using microfrontends developed in separate angular projects as webcomponents. Each microfrontend has its own ngrx-store. I think, the state is working correctly. But the devtools are not working as expected. I explained the problem here ngrx/platform#2986
Additional infos:
My shell app starts with an "@@INIT" event. My initialstate is undefined. But it should contain a value.
My microfrontend starts with an "@ngrx/store/init" event and contains the initialstate of the shell app:)
After the first dispatch in each store, it seems working better. After using locking and unlocking button in the devtools, the state between the two apps partially changes from one store to the other. The initialstate of the shell app keeps in the wrong store.
Switching between root and feature states or settings the reducer later after window loaded doesn't help.
Any idea?
:)
Hi there all,
My team and i are working on an enterprise application with Angular and ngrx, i've been directed here via google after searching for an issue with immutability in ngrx and angular when using angular's DynamicComponentHostDirective and it's function "createComponent()". I saw that the issue can be solved by disabling the strictStateImmutability in app.module.ts and that works fine.
runtimeChecks: {
strictStateImmutability: false,
strictActionImmutability: false
},
My question is rather if there's any plans on solving this issue in ngrx, or if there's a workaround to enable strictStateImmutability while using the createComponent-function?
tapResponse instead of tap for any side effect related code, but I've noticed that tapResponse seems to swallow thrown errors (like "ReferenceErrors" etc), probably because of catchError(() => EMPTY) that's used inside of it. Is that how it's supposed to work?
tap instead?
@piotrpalek The syntax you're describing is wrong though? catchError() shouldn't be inside tapResponse()but instead you should use common callback-functions in tapResponse(), as docs describe it:tapResponse<T>(nextFn: (next: T) => void, errorFn: (error: unknown) => void, completeFn?: () => void): (source: Observable<T>) => Observable<T>
I also don't think tapResponse() and catchError() should be used alongside one another.
In our enterprise-project, we use tap() to handle side effects (an simple example is console.log). And catchError() to handle errors that have occured. And in case we want to do things regardless of error or not we use finalize()-operator. I can be wrong but this is how we handle it.
tapResponse? It just gets silently swallowed
I somehow need to know the ids before passing objects to the reducer.
