Pierre A. Duchateau

> @paduc I simply want a similar control flow to this https://doc.rust-lang.org/std/result/. An example is > > ```rust > fn write_info(info: &Info) -> io::Result { > // Early return on...

You are right about rust being the inspiration for this library but I didn’t create it, @supermacro did 😉. I’m just a contributor. The PR uses generators which I’m not...

@Enteee I'm also interested in plantuml => typescript => plantuml generation/parsing. My use-case is reduced in scope as I want to create / update the boilerplate for a DDD design...

@Enteee after putting more thoughts into my goal, I believe I'm going to need something more complex than plantuml => typescript => plantuml as I need to include generation rules...

Je suis preneur aussi ! J'ai lancé un projet avec ce template il y a une semaine, j'aimerais savoir au plus vite si je dois changer de cap...

Merci pour l'update @thimy ! Le futur design system serait-il disponible en avant-première pour qu'on commence le travail de pré-intégration ?

Hi @timvandam, I’m having a hard time understanding what you want to do. Could you provide a more complete example ?

Thanks @timvandam. Reading [this](https://stackoverflow.com/questions/24662289/when-is-thensuccess-fail-considered-an-antipattern-for-promises) also helped me grasp the topic. Wouldn't the best solution be to mimick `Promise.then` and accept a second function argument to `Result.andThen`, instead of adding a...

In my opinion, it's valuable to have an API with a clear distinction between the Result/ResultAsync "world" (eg andThen, orElse, map, mapErr, ... all methods with a `Result => Result`...

This is how I normalize: ```ts const myResultAsync = okAsync().andThen(() => myUnknownResult); ```