Skip to content

Export NavigationGuardProviderContext #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Export NavigationGuardProviderContext #25

wants to merge 2 commits into from

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

@jackstenglein
Update README.md
77e5c25 
Adds instructions on using exported NavigationGuardProviderContext and clarifies custom dialog example
@jackstenglein
Copy link
Author

@peinguin Updated the README

peinguin
peinguin approved these changes Feb 12, 2025
View reviewed changes
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@peinguin peinguin peinguin approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@jackstenglein @peinguin