-
Notifications
You must be signed in to change notification settings - Fork 1
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
2.0.0 Release #6
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # README.md
…Mind/Processed into 1-evaluate-timeout-functionality
…Mind/Processed into 1-evaluate-timeout-functionality
# Conflicts: # Changelog.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New
ProcessSupport
andLoadableSupport
, you now don't need to provide explicitself
anymore, since those closures are simply passed into aTask
, so reference cycles are no real concern@Loadable
and@Process
(as well as their protocol counterparts)run
methods of theProcessSupport
protocol are now isolated to theMainActor
LoadableState<Value>.map(transform:)
to allow convenient mapping of loadable values.@Loadable
and@Process
that give access to a SwiftUI binding to the underlyingLoadableState
andProcessState
:$process.binding
and$loadable.binding
.@TaskIdentifier
property wrapper, which is a convenience wrapper around aUUID
SwiftUI state that helps with task restarts, e.g..task(id: taskIdentifier) { ... }
Restartable Loadable
,Refreshable Loadable
,Process Interrrupts
,Loadable Interrupts
andFailure Alert Process
ResetProcess
andResetLoadable
that can be thrown to reset a process or loadabletypealias SingleProcessState = ProcessState<SingleProcess>
for convenienceChanged
ProcessID
toProcessKind
to better communicate its purpose. This should not affect your code at all.Fixed
ProcessSupport
protocol code to simplify implementationCancelProcess
andCancelLoadable
error behavior inProcessSupport
andLoadableSupport
; they used to perform a reset instead of a cancelTask
priority
argument in an overload of theProcess.run
method