Skip to content

Conversation

jackstenglein
Copy link

This allows users of this library to hook into the guardMapRef value and build their own custom functionality on top of it.

@peinguin
Copy link
Contributor

I would like to see README changed in this PR to show how to use this new export

Adds instructions on using exported NavigationGuardProviderContext and clarifies custom dialog example
@jackstenglein
Copy link
Author

@peinguin Updated the README

Copy link
Contributor

@peinguin peinguin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be honest, I do not see why need to use next-navigation-guard if there is "a special routing setup that prevents you from using the built-in NextJS router".

However, I think, it will harm no one to get a list of active guards.

@jackall3n
Copy link

This would be really helpful as it give us easy access to the guardMapRef value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants