Open saffabook opened 4 years ago
@arturovt what do you think?
anybody out there?
@ngxs/core ping
@ngxs/core ping ping ding aling?
@saffabook if you can investigate problem, maybe will be can you create PR for fix current bug?
I have the similar issue. So, I dispatch event with async handler multiple times and cancel all of them. After it, all new actions will be logged on the some level above in the console (equivalent to the canceled actions).
important to note that actions are really canceled, just logging-plugin doesn't reset the depth of logs.
Affected Package
The issue is caused by package @ngxs-logger-plugin.js
Description
Weird indentation on ngxs-logger.
I am following this tutorial, particularly the {cancelCompleted: true} functionality for NGXS.
If you follow the video, you will see him click quickly on an order to demonstrate how the request is cancelled followed by a new request. However in his example, his ngxs-logger, the console log indents with the request, and then it all resets when completed. I have an image of it below. Also you can see several green Next State comments. Also have a look at the video to see what I mean.![image](https://user-images.githubusercontent.com/6928921/90426821-55757c80-e0ca-11ea-9558-e26d8cc43eb1.png)
However with mine, my ngxs-logger remains indented and never resets. I have an image below to explain what I mean. Also I have only one green next state despite clicking multiple times. My server is on a 3 second delay so I can mimic any lag. Does this lag have anything to do with it?![image](https://user-images.githubusercontent.com/6928921/90427027-a2595300-e0ca-11ea-9e8e-8df41fed724d.png)
Hi I have written a more in depth article on stack overflow.
I have the exact code I am using on Stackblitz
Why would my ngxs-logger behave differently to the tutorial.
Many thanks.