-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Remove lazy #433
Remove lazy #433
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments:
- The code should be reviewed for places where
Effect|Query.succeed
was being used to convert aLazyArg
to a value. These should be removed if theLazyArg
was removed. I've tried to note these situations where I saw them. - The
orElse*
,orFail*
, and generally any constructors that accept an error should probably remain lazy (as we have done in thecore
library)
Thanks a lot for your comments! Helped me understood deeply why some where lazy and some non-lazy in core! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problem at all 😃
The only thing left is to make sure that the version PR will get triggered. To do that, you can run the following command:
yarn changeset
and follow the prompts in your shell. I would suggest incrementing patch versions for now, since that's what we're doing in core
until v1.0.0
.
Additionally, I would suggest squashing all the commits in this PR into one commit locally (after running the changesets command above). This will ensure a nice clean update to the CHANGELOG can be made.
f33afbd
to
88f6af7
Compare
No description provided.