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

Qualify Send as Effect(Task)<Action>.Send #1926

Merged
merged 4 commits into from
Feb 18, 2023

Conversation

tgrapperon
Copy link
Contributor

@tgrapperon tgrapperon commented Feb 18, 2023

I've qualified a few missed occurrences of unqualified Send that I missed in #1911. I can rebase these changes in main if you prefer.
I've used EffectTask as this alias is still used through the codebase.
This should fix #1924

@tgrapperon
Copy link
Contributor Author

I've also fixed a few tests expectations. I don't think they were induced by #1911. It would probably be preferable to update all the internal EffectTask to Effect soon.

@tgrapperon
Copy link
Contributor Author

As EffectTask was already renamed in the documentation, I took the liberty to perform the change through the whole codebase. Only the deprecated typealias is preserved.

This should be more resilient when this extension will become an `Effect` extension rather than `EffectPublisher<_, Never>`.
@tgrapperon
Copy link
Contributor Author

tgrapperon commented Feb 18, 2023

If you prefer to push only the fix from prerelease/1.0 directly, it merely consists in searching and replacing all occurrences of Send { by EffectTask<Action>.Send {.

Copy link
Member

@stephencelis stephencelis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks!

@stephencelis stephencelis merged commit ceca49f into pointfreeco:prerelease/1.0 Feb 18, 2023
@tgrapperon tgrapperon changed the title Qualify Send as Effect(Task)<Send> Qualify Send as Effect(Task)<Action>.Send Feb 18, 2023
@mbrandonw mbrandonw mentioned this pull request Feb 20, 2023
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

Successfully merging this pull request may close these issues.

2 participants