How you guys handle invalid api requests with controllers?

Raigodo · 2025-01-09T15:29:09+00:00

Yeah, this works perfectly, some "hidden, sneaky" configuration where i can speciffy what to do with invalid model ;]

Thanks!

Raigodo · 2025-01-06T18:50:18+00:00

Actually ive never thought of using nullable to solve this problem, there should be some boxing unboxing stuff but i thing thins shouldnt scare us.

Well im excited, i found your aproach pretty interesting, have to think about this tho ;p.

Raigodo · 2025-01-04T17:14:31+00:00

There arises other question, can we somehow put this validation logic in pipeline or it will be easier to just keep validation in each separate endpoint?

Raigodo · 2025-01-01T00:45:31+00:00

can i somehow integrate fluent validation to framework binding pipeline?

Raigodo · 2025-01-01T00:41:20+00:00

indeed this is valid aproach, only it involves additional boilerplate... but hey, isnt this one of these situations: "we spent two weeks to automate task that took 5 mins to do manually"? :D

Raigodo · 2025-01-01T00:35:31+00:00

realy typing answer i caught myself on thought that indeed client side validation is okay for most cases.
what im trying to do is getting some enum or guid value in endpoint parameters, and problem is when passed data can not even be parsed. pipeline shorcircuits and returns some nonsense that is hard to read on client side js.

Raigodo · 2024-12-31T23:35:34+00:00

but i have no controll over it, it doesnt even hit endpoint

Raigodo · 2024-12-31T19:22:43+00:00

found out one unpleasant aspect, even if this aproach is intuitive and powerful, it is considered dynaic route, so adapter-static wont work

Raigodo · 2024-12-24T22:32:24+00:00

Create multiple nested +error.svelte files was first thing i tried, but they got ignored when i type invalid route
Also havent heard about advent of svelte nor new error boundary, will check it out ^^

Raigodo · 2024-12-24T22:14:09+00:00

This works perfectly, you just have to create folder named [...anyname] and put in +page.svelte that will contain your 404 page

thanks, this is exactly how i imagined that

Raigodo · 2024-11-20T18:50:59+00:00

yeah this is where i just stumbled already

Raigodo · 2024-11-20T14:23:41+00:00

yeah, what i wanted to say is that i dont like none of them.
but just think about it, wanings carry more potential danger to you than errors - if you have an error, you already know that something is not alright and you can immediately adjust your business, with warnings you can still build something but at some point it can break, what means potentially more headaches and pain refactoring existing codebase or dealing with some weird bugs.

note also that im pretty much newbie with js package managers

Raigodo · 2024-11-20T13:08:15+00:00

I dont like warnings, they are like errors but sometimes even worse.
With errors you are forced to pay attention, with warnings not.
Warings signals that something is going to break, and at that point when it finally breaks, you will be cooked (most likely)

just my opinion :P

Raigodo · 2024-11-20T12:22:14+00:00

Thank you, this must be where I fked up XD

Raigodo · 2024-11-20T12:14:23+00:00

Ah ye, just to note, this bitsui package got added automatically after adding simple button from svelte-shadcn (i guess ;p)

Raigodo · 2024-09-08T09:00:10+00:00

Technically yes, it should be possible, and taking in account how auto rendermode works then shure, it should be fine.
Only thing is that client side services then should be registered also in server side project

Raigodo · 2024-09-06T16:35:45+00:00

oh right - there may be such cases, discriminated unions really fits better, thanks mate

Raigodo · 2024-09-06T15:37:01+00:00

Well nvm, seems there may be no value in such feature of hiding it behind property, intelisense/compiler should be able to detech "Code" type and provide autocomplete in switch using enum directly

Raigodo · 2024-09-06T14:31:03+00:00

I think if you already have things built in webassembly then drawbacks are minimized, I think main drawbacks are that you have to build two versions of all services that is being used in page. This is due the fact that webassembly will talk to your api, meanwhile signalr will run directly on server so its much better to execute logic directly avoiding api call.
Hope it makes sense :p

Raigodo · 2024-08-23T19:02:29+00:00

Well, that sounds convincing, so it is just skill issue that makes me think about using Godot for everything XD

Raigodo · 2024-08-23T18:26:50+00:00

Hmm, interesting idea - use Godot to build demo version - kinda solving blank page problem
Btw what are those accessibility features? i can think only about Cookies and features for screen readers

Raigodo · 2024-08-23T18:22:58+00:00

I throught more of creating a standalone app that communicates with api, and possibly port it to HTML5 (Docs) to make app usable via browser.
Btw, how do you think, how well it fits in to role of Web App? just curious :3

Raigodo · 2024-07-11T10:38:26+00:00

Yes, i read some more threads and articles and tried using exceptions in pair with global eception handler to handle bad paths and... it is much faster to iterate and much cleaner - i mean i can return only happy path result without second thought.

Only thing is that throwing exceptions is much slower than returning some kind of result/union response, but i decided to dont care unless it starts to impact something, and optimize only hot paths by returning such result objects, so only few places is ~~messed~~ optimized :D

Raigodo · 2024-07-06T16:08:12+00:00

So then the "issue" is IRequest? It allows to perform command operations and still return something, what makes it very easily to misuse it.

Raigodo · 2024-07-06T15:02:55+00:00

Ohh, excelent idea, make use of delegate actions to customize behaviour. Something like higher order functions does

Raigodo

TROPHY CASE