You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
It seems like #2000 causes some regression.
Using autoLoginPartialRoutesGuard, the route's state is passed as configId causing issues because the config cannot be found.
Resulting in the following error:
core.mjs:6619 ERROR Error: Please provide a configuration before setting up the module
at _LoginService.login (login.service.ts:32:13)
at auto-login-partial-routes.guard.ts:137:24
at map.js:7:37
at OperatorSubscriber2._this._next (OperatorSubscriber.js:15:21)
at Subscriber2.next (Subscriber.js:34:18)
at Observable2._subscribe (innerFrom.js:51:24)
at Observable2._trySubscribe (Observable.js:38:25)
at Observable.js:32:31
at errorContext (errorContext.js:19:9)
at Observable2.subscribe (Observable.js:23:9)
In the example you can the configId which is used:
Steps to reproduce the behavior
You can reproduce this issue using the standalone example in this repo:
npm run build-lib
npm run start-sample-code-flow-standalone
A clear and concise description of what you expected to happen.
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Version
Latest (unreleased)
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
It seems like #2000 causes some regression.
Using
autoLoginPartialRoutesGuard
, the route's state is passed asconfigId
causing issues because the config cannot be found.Resulting in the following error:
In the example you can the configId which is used:
Steps to reproduce the behavior
You can reproduce this issue using the standalone example in this repo:
A clear and concise description of what you expected to happen.
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: