We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am learning TCA through tutorials.
I found an abnormal behavior for timer in Section 3 of https://pointfreeco.github.io/swift-composable-architecture/main/tutorials/composablearchitecture/01-04-composingfeatures.
After activating each timer in two tabs (tab1, tab2), if you cancel the timer in one tab, the timers in both tabs are canceled.
The same id, "CancelID.timer" (enum case), is registered in the .cancellable(id:) method, so even if only one is canceled, both seem to be cancelled.
I think this behavior is different from what the tutorial intended.
main
The timer on each tab operates “independently.”
If you cancel the timer on one tab, the timer on the other tab will also be canceled.
Please refer to Section 3(Deriving child stores) of https://pointfreeco.github.io/swift-composable-architecture/main/tutorials/composablearchitecture/01-04-composingfeatures.
1.15.0
iOS 18
Xcode 16.0
swift-driver version: 1.115 Apple Swift version 6.0 (swiftlang-6.0.0.9.10 clang-1600.0.26.2) Target: arm64-apple-macosx15.0
The text was updated successfully, but these errors were encountered:
Fix issue pointfreeco#3417: Add unique ID for independent timer opera…
3043d10
…tion
No branches or pull requests
Description
I am learning TCA through tutorials.
I found an abnormal behavior for timer in Section 3 of https://pointfreeco.github.io/swift-composable-architecture/main/tutorials/composablearchitecture/01-04-composingfeatures.
After activating each timer in two tabs (tab1, tab2), if you cancel the timer in one tab, the timers in both tabs are canceled.
The same id, "CancelID.timer" (enum case), is registered in the .cancellable(id:) method, so even if only one is canceled, both seem to be cancelled.
I think this behavior is different from what the tutorial intended.
Checklist
main
branch of this package.Expected behavior
The timer on each tab operates “independently.”
Actual behavior
If you cancel the timer on one tab, the timer on the other tab will also be canceled.
Reproducing project
Please refer to Section 3(Deriving child stores) of https://pointfreeco.github.io/swift-composable-architecture/main/tutorials/composablearchitecture/01-04-composingfeatures.
The Composable Architecture version information
1.15.0
Destination operating system
iOS 18
Xcode version information
Xcode 16.0
Swift Compiler version information
The text was updated successfully, but these errors were encountered: