ngneat/elf

ELF not propagating the Error

luishcastroc opened this issue · 4 comments

luishcastroc commented

Which @ngneat/elf-* package(s) are the source of the bug?

requests-status

Is this a regression?

No

Description

I'm trying to see what will be the best path to track when a request was done properly or in ERROR so I used ELF trackRequestResult however the error doesn't seem to be propagating as it will normally do.

Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-ivy-fgbbij

Please provide the exception or error you saw

I added another library to track Errors easily and seems it's as well used in the project (rx-angular/template) however in the minimal reproduction I see the error clearly propagated.

Error: { "headers": { "normalizedNames": {}, "lazyUpdate": null, "headers": {} }, "status": 404, "statusText": "Unknown Error", "url": null, "ok": false, "name": "HttpErrorResponse", "message": "Http failure response for (unknown url): 404 undefined", "error": null }

when i use the ELF selector that is supposed to have the same error

Error: false

i actually see the error in the console for both cases.

Please provide the environment you discovered this bug in

No response

Anything else?

No response

Do you want to create a pull request?

No

NetanelBasal commented

Could you please clean all the others and leave only Elf? It's hard to tell what's going on.

luishcastroc commented

Could you please clean all the others and leave only Elf? It's hard to tell what's going on.

Removed the first scenario and i just let the ELF related thing, please let me know if is better like this, as well i noticed that the error seems to be there when i use the API for trackingResults however when i want to destructure the error property it will tell me is not there.

thanks