Simon Green

I'm a big fan of packages working against the default handler interfaces when possible. It may be that if something doesn't work with those then it might be better to...

Yes, once you load a view it stays loaded so if you've set an observer it will keep updating. I tried to explain what's going on and give some options...

I had a go at creating something to help with the SEO / meta-tag updating. Here's what I came up with (any feedback appreciated): https://github.com/CaptainCodeman/app-metadata I tested it out by...

Use the `auto` property, set it to the flag for whatever you need.

For security you need to check auth on _every_ request. Every route can be fetched directly, without using the app UI at all, and each fetch is independent of anything...

As a fundamental rule, authorization _has_ to happen on each request to the server before data is loaded and returned (and making the load incorporate the user identity or role...

Either way, you have to remember to add every route to the list - it's safer to apply something to each route to define what permission checks need to be...

I think that example makes it appear way worse than it really is. Having repeated `authGuard` functions in each server load makes it look way more onerous to do auth...

I'm not sure, but it sounds like you _might_ want to just move the data fetching up to a layout so it stays constant while those params change. I have...

Personally, I'd put something like that in the page head block, to set a class or css property that can show or hide things. That way every page is identical...