Updated Kotlin to 2.0.0, coroutines to 1.8.1, enabled klib API validation

[arkivanov]

Summary by CodeRabbit

• New Features

  • Introduced back handling functionality with new classes and interfaces for managing back navigation and events.
  • Added instance keeping functionality for managing instances and their lifecycle.
  • Added coroutine-related functionality for lifecycle management in Kotlin multiplatform projects.
  • Introduced lifecycle management and disposable scopes functionality.

• Chores

  • Updated .gitignore to exclude the .kotlin directory.
  • Updated Kotlin, Kotlinx Binary Compatibility Validator, Kotlinx Coroutines, and Detekt Gradle Plugin to their latest versions.
  • Updated the version of the gradle-setup-plugin.

[coderabbitai]

Walkthrough

This update introduces several new functionalities across multiple components, focusing on enhancing back handling, instance keeping, lifecycle management, and state keeping. Key changes include new methods and properties in the back-handler, instance-keeper, and lifecycle modules, updated dependencies in build.gradle.kts, and version upgrades in deps.versions.toml. Additionally, the .gitignore file now excludes the .kotlin directory.

Changes

Files/Directories	Change Summary
.gitignore	Updated to exclude the .kotlin directory.
back-handler/api/back-handler.klib.api	Added new methods and properties for back handling functionality.
build.gradle.kts	Added import and configuration for BinaryCompatibilityValidatorConfig.
deps.versions.toml	Updated versions for Kotlin, Kotlinx Binary Compatibility Validator, Kotlinx Coroutines, and Detekt Gradle Plugin.
instance-keeper/api/instance-keeper.klib.api	Introduced new methods and properties for instance keeping functionality.
lifecycle-coroutines/api/lifecycle-coroutines.klib.api	Added new coroutine-related functions for lifecycle management.
lifecycle-reaktive/api/lifecycle-reaktive.klib.api	Added functions for lifecycle management and disposable scopes.
lifecycle/api/lifecycle.klib.api	Introduced interfaces and classes for lifecycle management.
settings.gradle.kts	Updated version of the gradle-setup-plugin.
state-keeper/api/state-keeper.klib.api	Introduced methods and functions for state keeping and serialization.

Poem

In the code's enchanted glade,
New features now cascade,
Back handling's more refined,
Instances well-defined,
Lifecycles gracefully flow,
States in harmony grow,
A coder's dream, aglow! 🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between eece207 and c871033.

Files ignored due to path filters (1)

• kotlin-js-store/yarn.lock is excluded by !**/*.lock

Files selected for processing (10)

• .gitignore (1 hunks)
• back-handler/api/back-handler.klib.api (1 hunks)
• build.gradle.kts (2 hunks)
• deps.versions.toml (1 hunks)
• instance-keeper/api/instance-keeper.klib.api (1 hunks)
• lifecycle-coroutines/api/lifecycle-coroutines.klib.api (1 hunks)
• lifecycle-reaktive/api/lifecycle-reaktive.klib.api (1 hunks)
• lifecycle/api/lifecycle.klib.api (1 hunks)
• settings.gradle.kts (1 hunks)
• state-keeper/api/state-keeper.klib.api (1 hunks)

Files skipped from review due to trivial changes (3)

• .gitignore
• deps.versions.toml
• settings.gradle.kts

Additional comments not posted (29)

lifecycle-reaktive/api/lifecycle-reaktive.klib.api (2)

9-9: LGTM! The addition of disposableScope to LifecycleOwner enhances resource management in reactive streams by tying it to the lifecycle.

---

10-10: LGTM! The withLifecycle function is a valuable addition for lifecycle-aware management of disposables.

build.gradle.kts (2)

2-2: LGTM! Importing BinaryCompatibilityValidatorConfig is necessary for the new binary compatibility validation configuration.

---

75-75: LGTM! Enabling binary compatibility validation for klib is a crucial step for maintaining API stability.

lifecycle-coroutines/api/lifecycle-coroutines.klib.api (5)

9-9: LGTM! The coroutineScope function provides a lifecycle-aware CoroutineScope, enhancing coroutine management in lifecycle-bound components.

---

10-10: LGTM! The withLifecycle function is a valuable addition for lifecycle-aware management of CoroutineScope.

---

11-11: LGTM! The flowWithLifecycle function is crucial for lifecycle-aware stream management, ensuring that flows are paused and resumed in sync with lifecycle states.

---

12-12: LGTM! Extending Flow with withLifecycle allows for precise control over stream lifecycle, which is beneficial for resource management.

---

13-14: LGTM! The repeatOnLifecycle functions are essential for re-invoking tasks in response to lifecycle changes, enhancing robustness and responsiveness of lifecycle-aware components.

instance-keeper/api/instance-keeper.klib.api (5)

9-12: LGTM! The methods added to InstanceKeeper enhance its functionality by allowing more flexible instance management, crucial for state persistence across lifecycle events.

---

13-14: LGTM! Adding onDestroy to Instance allows for explicit cleanup actions, which is essential for managing resources efficiently.

---

16-19: LGTM! The SimpleInstance class provides a straightforward and effective way to manage lifecycle-aware instances, enhancing resource management.

---

22-23: LGTM! The addition of destroy to InstanceKeeperDispatcher allows for explicit and controlled destruction of instances, which is crucial for avoiding resource leaks.

---

25-27: LGTM! The InstanceKeeperOwner interface provides essential access to InstanceKeeper, facilitating easier instance management within components.

state-keeper/api/state-keeper.klib.api (5)

9-13: LGTM! The methods added to StateKeeper enhance its functionality by allowing more flexible state management, crucial for persistence across lifecycle events.

---

15-16: LGTM! The addition of save to StateKeeperDispatcher allows for explicit and controlled saving of state, which is crucial for ensuring state persistence.

---

18-20: LGTM! The StateKeeperOwner interface provides essential access to StateKeeper, facilitating easier state management within components.

---

22-26: LGTM! The SerializableContainer class provides essential methods for managing serialized state, enhancing data persistence and manipulation capabilities.

---

31-35: LGTM! The additional serialization functions provide granular control over serialization processes, enhancing the robustness and flexibility of state management.

back-handler/api/back-handler.klib.api (5)

9-30: LGTM! The methods added to BackCallback enhance its functionality by providing more granular control over back navigation events, crucial for complex navigation scenarios.

---

32-41: LGTM! The methods added to BackDispatcher enhance its functionality by providing predictive back handling capabilities, crucial for anticipatory navigation scenarios.

---

42-45: LGTM! The methods added to BackHandler enhance its functionality by allowing dynamic registration and unregistration of back callbacks, crucial for flexible navigation management.

---

47-49: LGTM! The BackHandlerOwner interface provides essential access to BackHandler, facilitating easier back navigation management within components.

---

51-77: LGTM! The methods added to BackEvent enhance its functionality by providing detailed control over the components of back events, crucial for precise navigation management.

lifecycle/api/lifecycle.klib.api (5)

12-13: The subscribe and unsubscribe methods are well-implemented for lifecycle event management.

---

15-20: Lifecycle event methods in the Callbacks interface are appropriately named and structured.

---

36-38: The LifecycleOwner interface correctly provides access to the Lifecycle, essential for lifecycle-aware components.

---

42-47: Lifecycle management methods in LifecycleRegistry are well-defined, covering all necessary states and transitions.

---

63-69: The ApplicationLifecycle class provides a robust framework for managing application-wide lifecycle events, ensuring consistency and reliability.