-
Notifications
You must be signed in to change notification settings - Fork 23
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.
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
feat: add possibility to surcharge next router listener #88
feat: add possibility to surcharge next router listener #88
Conversation
@m-maillot @Viczei @carolineBda Vous en pensez quoi ? De mon côté, je pensais propager d'autres valeurs supplémentaires comme D'ailleurs ça peut poser soucis ici car on ne va pas le setter |
Codecov ReportBase: 85.00% // Head: 86.15% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #88 +/- ##
==========================================
+ Coverage 85.00% 86.15% +1.15%
==========================================
Files 1 1
Lines 60 65 +5
Branches 16 20 +4
==========================================
+ Hits 51 56 +5
Misses 1 1
Partials 8 8
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
# [1.5.0](v1.4.0...v1.5.0) (2023-01-13) ### Features * add possibility to surcharge next router listener ([#88](#88)) ([f1bf4a2](f1bf4a2))
🎉 This PR is included in version 1.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This branch allows users to surcharge the method from Next.js router
onChangeStart
andonChangeComplete
that is used in the library