ningle route requirements - what happens when they are not met?

[martianhi]

i just read through tutorial 11, thanks for it.

i'm interested in your use of requirements. i think in my own login set up, a route will just have a function with an if flow control structure in it: if not logged-in-p, redirect (to prev page or login page) + flash user-error. when you turn logged-in-p into a ningle requirement, it does seem elegant, but i wonder how you handle the failure case? if you can't load the given route, do you redirect somehow?

thanks again

[nmunro]

So my intended use was that some routes absolutely shouldn't be accessible without being authenticated.

I don't want to pretend to know if this was an intended use of requirements, I really couldn't find a lot of documentation or best practices around ningle (hence why I have written what I have), but it seemed like a logical use case for requirements.

I havent seen this fail in practice, and I suppose if an authentication check fails and causes an error and a route to fail to load, the issue might be elsewhere and the app has bigger problems.

Having said all that, am happy to collaborate and maybe build a package to make it a little more robust if any real world examples of this being a problem can be found.

[martianhi]

ah ok, thanks for clarifying. somehow i failed to grasp that from the tutorial. in that case, i stick with my redirects/flashes. i also had struggled to grok ningle's requirements, so basically ignored them. but i can see now how they could be useful, thanks to your explorations. Neil Munro ***@***.***> writes:

…

* nmunro left a comment (nmunro/ningle-tutorial-project#11) So my intended use was that some routes absolutely shouldn't be accessible without being authenticated. I don't want to pretend to know if this was an intended use of requirements, I really couldn't find a lot of documentation or best practices around ningle (hence why I have written what I have), but it seemed like a logical use case for requirements. I havent seen this fail in practice, and I suppose if an authentication check fails and causes an error and a route to fail to load, the issue might be elsewhere and the app has bigger problems. Having said all that, am happy to collaborate and maybe build a package to make it a little more robust if any real world examples of this being a problem can be found. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.

-- some writing: https://anarchive.mooo.com an internets: https://pleasantlybabykid.tumblr.com/

[nmunro]

So a requirement appears to be a function of one parameter (and if you need more, youll need to pass a list or other complex type to hold values), and it allows you to modify routing behaviour. If you know by what condition you want your if/else to do, and you can derive that from some state, requirements should do what you want.