Change active and exact-active behavior for router-link

[posva]

Rendered

Make active matching more consistent by avoiding existing caveats by design

• Is this breaking change bringing more value than the old behavior?
• Are any of the alternatives listed more desirable?
• Do you need the exact prop?

Please, vote with 👍 and 👎 if this is something you want or not

[posva]

I added a few examples about the breaking change that should make this RFC clearer

[posva]

I added a section about aliases to explain how they behave with the active behavior

[posva]

Added a section about nested absolute aliases

[posva]

This RFC is now in final comments stage. An RFC in final comments stage means that:

The core team has reviewed the feedback and reached consensus about the general direction of the RFC and believe that this RFC is a worthwhile addition to the framework.
Final comments stage does not mean the RFC's design details are final - we may still tweak the details as we implement it and discover new technical insights or constraints. It may even be further adjusted based on user feedback after it lands in an alpha/beta release.
If no major objections with solid supporting arguments have been presented after a week, the RFC will be merged and become an active RFC.