3 ms·
> Routing is solved by community packages Its a bit awkward in places. Like if you want to receive a server-side web-hook, Iron Router is really the only way
by jonmc12 11y ago
> Routing is solved by community packages
Its a bit awkward in places. Like if you want to receive a server-side web-hook, Iron Router is really the only way to go. But, lets say you have an Angular client, Iron Router can't be disabled on client when being used on the server. Now you have to hack for Iron Router and Angular UI router to play together nicely - using 2 routers on client because you want to receive server-side webhooks is obviously not ideal. But, at the same time both the community and the roadmap are coming together to make solutions workable before being fully 'solved', imo.
- Bjartr 11y agoIf there had been an official router, what's to say it wouldn't have had the same problem?
- rglover 11y agoThere are separate server-only routers. Here's a tutorial I whipped up: https://themeteorchef.com/snippets/server-side-routing-with-picker https://themeteorchef.com/snippets/server-side-routing-with-.... This would remove the need for a dependency on Iron Router on the client.