Support for client routing by explicit Links

[jahredhope]

As I understand it VPS will inject an event listener to monitor for any <a /> tags being clicked when Client Routing is enabled.

I'm familiar with React Router and other alternatives that require explicit <Link /> components, rather than listening on all links. I generally try and avoid global behaviour when possible, and so I wanted to move to React Router's pattern.

I've attempted to re-create this behaviour by disabling clientRouting and creating my own Link component that calls navigate. However, there doesn't appear to be a way to opt into the client router in general, whilst opting out of the global onLinkClick behaviour specifically.

So my question is, can I have my cake and eat it to? 🍰 Can I use clientRouting, enjoy all the benefits of VPS's routing solution, whilst allowing me to handle the Link/navigate behaviour myself without global injection?

If not, I'd also be happy to be told why what I'm asking for is a bad idea, I'm very early on in a project so very happy to pivot.

Any advice is appreciated, thank-you for the awesome project.

[brillout]

I'm not aware and I don't see any drawbacks with VPS's approach. Hence, I'd recommend to stick to the beaten path, i.e. to how VPS intercepts clicks. Let me know if you run into any issue with that.

[brillout]

@Irrelon Have you seen #918 (comment)? It seems like it would unblock you.

[Irrelon]

@brillout Thanks, I think this will work. Will test...

[brillout]

@Irrelon 👍 Let me know how it goes. FYI I agree with everything you said, e.g. it would be nice for Route Functions to be able to opt-out. Also, in case your company is up for it, we're looking for sponsors (#1350).

[Irrelon]

@brillout It works! Thanks. Regarding sponsorship, this is a possibility. I'll have a chat with the team :)

[brillout]

Great, I'm glad it works. Ok neat let me know how it goes!

[brillout]

Closing in favor of #918.