---
title: "Comment by David Novák on \"Practical Guide to Fp-ts P5: Apply, Sequences, and Traversals\" | Hashnode"
description: "So far I was able to get around this error by manually specifying error types: sequenceS(E.either as E.as apply.Apply2C< 'Either', ValidateEmailError"
url: "https://hashnode.com/posts/practical-guide-to-fp-ts-part-5/6071bd511494367be6d29fcf/comment/642be9ccae2a7e0743394182"
---

[Discussion](https://hashnode.com/posts/practical-guide-to-fp-ts-part-5/6071bd511494367be6d29fcf)

Comment [Practical Guide to Fp-ts P5: Apply, Sequences, and Traversals](https://hashnode.com/posts/practical-guide-to-fp-ts-part-5/6071bd511494367be6d29fcf)

[David Novák](https://hashnode.com/@kaladivo)

[Apr 4, 2023](https://hashnode.com/posts/practical-guide-to-fp-ts-part-5/6071bd511494367be6d29fcf/comment/642be9ccae2a7e0743394182)

So far I was able to get around this error by manually specifying error types:

sequenceS(E.either as E.as apply.Apply2C< 'Either', ValidateEmailError | ValidatePasswordError)({ email: validateEmail(email), password: validatePassword(password), })

But it still is not pretty.