Skip to content

CanDeactivate guard documentation doesn't state when "nextState" can be undefined #47153

@MinaFayez9

Description

@MinaFayez9

Description

I can't find in any place in the documentation a reference for when "nextState" property of the "CanDeactivate" might be sent by undefined and what is the logic behind it, so could you please explain it here and update the documentation about it ?

What is the affected URL?

https://angular.io/api/router/CanDeactivate

Please provide the steps to reproduce the issue

No response

Please provide the expected behavior vs the actual behavior you encountered

No response

Please provide a screenshot if possible

No response

Please provide the exception or error you saw

No response

Is this a browser-specific issue? If so, please specify the device, browser, and version.

No response

Metadata

Metadata

Assignees

Labels

P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: routerrouter: guards/resolvers

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions