Skip to content

Add Effect.send #1859

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

Merged
merged 6 commits into from
Jan 24, 2023
Merged

Add Effect.send #1859

merged 6 commits into from
Jan 24, 2023

Conversation

stephencelis
Copy link
Member

With the Effect<Action, Failure> -> Effect<Action> migration, Effect.init(value:) and Effect.init(error:) no longer make sense. We will be retiring the latter some time in the future, so let's also get a head start and rename the former to Effect.send.

For now it will call Effect.init(value:) under the hood, but in the future we will want a non-Combine-driven way of running synchronous effects.

With the `Effect<Action, Failure>` -> `Effect<Action>` migration,
`Effect.init(value:)` and `Effect.init(error:)` no longer make sense. We
will be retiring the latter some time in the future, so let's also get a
head start and rename the former to `Effect.send`.

For now it will call `Effect.init(value:)` under the hood, but in the
future we will want a non-Combine-driven way of running synchronous
effects.
@stephencelis stephencelis merged commit e294b24 into main Jan 24, 2023
@stephencelis stephencelis deleted the effect-send branch January 24, 2023 00:41
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