Yes! the railway-oriented is interesting; things like F# are very cool.
In those scenarios, IMHO, categorization in error handling is important. For example: 1) non-functional validations and 2) business validations. In the first case, for (1), it can be solved through middlewares and pipelines. And for (2), you can use the notification pattern; libraries like Fluent Validation could help. Anyway, it depends...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes! the railway-oriented is interesting; things like F# are very cool.
In those scenarios, IMHO, categorization in error handling is important. For example: 1) non-functional validations and 2) business validations. In the first case, for (1), it can be solved through middlewares and pipelines. And for (2), you can use the notification pattern; libraries like Fluent Validation could help. Anyway, it depends...