Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using Do(E.either) results in "deprecated" warning #83

Open
huntwj opened this issue Jun 22, 2021 · 1 comment
Open

using Do(E.either) results in "deprecated" warning #83

huntwj opened this issue Jun 22, 2021 · 1 comment

Comments

@huntwj
Copy link

huntwj commented Jun 22, 2021

🐛 Bug report

Current Behavior

Using the Either type with the Do notation is marked as deprecated with the message "Use small, specific instances instead."

Do(E.either) // <-- `either` is marked deprecated
  .bind("name", value)
  .return(({name}) => ({out: name}));

Expected behavior

It has no compiler warnings or errors.

Reproducible example

See above

Suggested solution(s)

Should either really be deprecated, or is there an alternate "smaller" type that we can use in these places?

Additional context

n/a

Your environment

Which versions of fp-ts-contrib are affected by this issue? Did this work in previous versions of fp-ts-contrib?

Software Version(s)
fp-ts 2.5.3
fp-ts-contrib 0.1.26
TypeScript 3.9.6 (build) and 4.3.2 (editor)
@gcanti
Copy link
Owner

gcanti commented Jun 23, 2021

Looks like you are using [email protected] (where E.either is deprecated). You can use E.Monad instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants