2 ms·
> no API controllers ... I've got elegant LINQ statements right in my component markup. You do need to be careful with requirements before choosing this tight
by mycall 7y ago
> no API controllers ... I've got elegant LINQ statements right in my component markup.
You do need to be careful with requirements before choosing this tight binding. If you want single source, that's a great idea. If you need single source for mobile web + mobile app, you will be duplicating code. There are other reasons for API and business logic remaining server side.
> . If you find yourself reading the documentation for a CookiePolicyOptions or ClaimsPrincipal type, you probably went too far down the rabbit hole.
How do you suggest performing method authorization without claims?
- bob1029 7y agoThere is nothing stopping you from developing razor components which are capable of dynamically adjusting depending on the specific device you are targeting. You can add some JS interop to handle these queries, and then pass the device type information as a cascading parameter to all components from the top. I am not sure what sort of authorization schemes you are concerned with. All I use the cookies for is looking up an active user session via whatever SHA256 token is stored there (if any).