Using Either to structure your validations 

very nice, could you do a video about Task or whatever your approach is to side effect management?

So fp-ts Either is right biased... sad:(

I'm just starting down this path of learning fp-ts and you have been a great resource on this journey. One question I have is when to use the function declaration of "function validateUser(user)" vs "const validateUser = (user) => " These seem to do the same thing and are just a syntactical difference, but I haven't seen anything really explain why you would use one over the other. Also kind of on the same thread, I've seen you use interface, but is there a reason to use "interface" vs "type" declaration? Just trying to learn best practices as I go.

More FP tutorials please

It would be cool if you could upload your code to github so people can look at it after the video. Thanks

Thank you for this!

Can you do a video explaining the Either functions more? Like what is the difference of E.map and E.chain ? Also as @ms23605 mentioned, chaining, branching, working with promises would be awesome.

FInally someone who does videos on this which are more understandable :D

Would be good to know how you then work with the validated either (it could have one of two error messages or it could be right so how do you set up your logic branching). Also looking forward to TE and the K and W chainEithers

You’re a really good teacher by the way, showing progress and justification by working up from a non-optimal solution to a fp-better solution. (I know better here is in quotes as it is all subjective. But you know what I mean… 😄)

I really like how you construct your tutorials, keep up the good work!

Hey, @RyanDavisDev great content. I would love to see a video that is like an overview of `fp-ts`. I'm getting into FP with TS, and `fp-ts` is clearly the way to go. But as has been notable in several places, the barrier to entry is kinda high with the docs being so... terse.

Ryan we need more of your videos! Some TE advanced patterns would be cool

Very interesting video again, many thanks, hoping for more of it. 🎉

Thank you for these!

loving this content. keep it coming !

Thanks for the videos. Could you do a video on sequenceS and sequenceT?

Please, keep doing these videos! Thanks!

This was great, I love how you nitpicked and got into the details. I would love to see a series on io-ts as well!

There are a lot of weird patterns in this video. Why wrap `user` with `of` then chain when the first function you call takes a `User`? It is completely unnecessary. I have seen people make this "error" when composing functions with `pipe` because they think of it as the functional method chaining. It is more flexible than that. I am also sceptical about returning `Option` for the sake of adding your own error message. If you want to change the error message, you can simply use `mapLeft` without making `parseTime` fail with no useful error message for any of its callers. Parsing errors are not easily recoverable, but it's always nice to know when debugging that it encountered an unexpected token at a specific location for example. And if the error is recoverable, then you can use the error information to retry with `orElse` or you can figure out a fallback and use `getOrElse`.

JS objects wrapped in some crap, the author proudly calls Pipeable API. The name of this hype