NGXS - Handle action life cycle in actions$ stream
In one of my states, I cannot use the @Action(...)
annotation so I want to use the actions$ stream instead, like so
@State(...)
export class MyState implements NgxsOnInit {
constructor(private actions$: Actions) {}
ngxsOnInit(ctx: StateContext<any>): void {
this.actions$.pipe(ofActionSuccessful(MyAsyncAction)).subscribe(() => {
console.log('SUCCESS');
});
this.actions$
.pipe(
ofActionDispatched(MyAsyncAction),
tap(() => console.log('DISPATCHED')),
delay(1000),
map(() => console.log('DONE')
.subscribe();
}
}
Unfortunately, the logs in the console looks like "DISPATCHED", "SUCCESS" and then "DONE". Is there a way to handle actions life cycle while using the actions$ stream ? Or should I go the "old" way and then use a dedicated MyAsyncActionSuccess
action to handle this case ?
angular ngxs
add a comment |
In one of my states, I cannot use the @Action(...)
annotation so I want to use the actions$ stream instead, like so
@State(...)
export class MyState implements NgxsOnInit {
constructor(private actions$: Actions) {}
ngxsOnInit(ctx: StateContext<any>): void {
this.actions$.pipe(ofActionSuccessful(MyAsyncAction)).subscribe(() => {
console.log('SUCCESS');
});
this.actions$
.pipe(
ofActionDispatched(MyAsyncAction),
tap(() => console.log('DISPATCHED')),
delay(1000),
map(() => console.log('DONE')
.subscribe();
}
}
Unfortunately, the logs in the console looks like "DISPATCHED", "SUCCESS" and then "DONE". Is there a way to handle actions life cycle while using the actions$ stream ? Or should I go the "old" way and then use a dedicated MyAsyncActionSuccess
action to handle this case ?
angular ngxs
add a comment |
In one of my states, I cannot use the @Action(...)
annotation so I want to use the actions$ stream instead, like so
@State(...)
export class MyState implements NgxsOnInit {
constructor(private actions$: Actions) {}
ngxsOnInit(ctx: StateContext<any>): void {
this.actions$.pipe(ofActionSuccessful(MyAsyncAction)).subscribe(() => {
console.log('SUCCESS');
});
this.actions$
.pipe(
ofActionDispatched(MyAsyncAction),
tap(() => console.log('DISPATCHED')),
delay(1000),
map(() => console.log('DONE')
.subscribe();
}
}
Unfortunately, the logs in the console looks like "DISPATCHED", "SUCCESS" and then "DONE". Is there a way to handle actions life cycle while using the actions$ stream ? Or should I go the "old" way and then use a dedicated MyAsyncActionSuccess
action to handle this case ?
angular ngxs
In one of my states, I cannot use the @Action(...)
annotation so I want to use the actions$ stream instead, like so
@State(...)
export class MyState implements NgxsOnInit {
constructor(private actions$: Actions) {}
ngxsOnInit(ctx: StateContext<any>): void {
this.actions$.pipe(ofActionSuccessful(MyAsyncAction)).subscribe(() => {
console.log('SUCCESS');
});
this.actions$
.pipe(
ofActionDispatched(MyAsyncAction),
tap(() => console.log('DISPATCHED')),
delay(1000),
map(() => console.log('DONE')
.subscribe();
}
}
Unfortunately, the logs in the console looks like "DISPATCHED", "SUCCESS" and then "DONE". Is there a way to handle actions life cycle while using the actions$ stream ? Or should I go the "old" way and then use a dedicated MyAsyncActionSuccess
action to handle this case ?
angular ngxs
angular ngxs
edited Nov 22 '18 at 7:26
Nephidream
asked Nov 21 '18 at 21:36
NephidreamNephidream
787
787
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Might be related to this open issue. The library is not compatible with Redux Dev Tools. I believe NGXS is planning to ship it's own dev tools.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420798%2fngxs-handle-action-life-cycle-in-actions-stream%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Might be related to this open issue. The library is not compatible with Redux Dev Tools. I believe NGXS is planning to ship it's own dev tools.
add a comment |
Might be related to this open issue. The library is not compatible with Redux Dev Tools. I believe NGXS is planning to ship it's own dev tools.
add a comment |
Might be related to this open issue. The library is not compatible with Redux Dev Tools. I believe NGXS is planning to ship it's own dev tools.
Might be related to this open issue. The library is not compatible with Redux Dev Tools. I believe NGXS is planning to ship it's own dev tools.
answered Dec 5 '18 at 11:54
Reppin South StateReppin South State
82
82
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420798%2fngxs-handle-action-life-cycle-in-actions-stream%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown