ObsoleteWorkersApi
Marks all Worker
-related API as obsolete.
Workers are considered obsolete: their API shape, design, and behaviour have known flaws and pitfalls that are impossible to address in Worker's current form.
Workers continue being supported and maintained, but they eventually will be replaced with threads API and then deprecated.
It is not recommended to expose workers in public API or to have high coupling with Workers API, and instead, we suggest encapsulating them in a domain-specific API to simplify future migration and reduce potential exposure to dangerous API.
Since Kotlin
1.9Marks all Worker
-related API as obsolete.
Workers are considered obsolete: their API shape, design, and behaviour have known flaws and pitfalls that are impossible to address in Worker's current form.
Workers continue being supported and maintained, but they eventually will be replaced with threads API and then deprecated.
It is not recommended to expose workers in public API or to have high coupling with Workers API, and instead, we suggest encapsulating them in a domain-specific API to simplify future migration and reduce potential exposure to dangerous API.
Since Kotlin
1.9Marks all Worker
-related API as obsolete.
Workers are considered obsolete: their API shape, design, and behaviour have known flaws and pitfalls that are impossible to address in Worker's current form.
Workers continue being supported and maintained, but they eventually will be replaced with threads API and then deprecated.
It is not recommended to expose workers in public API or to have high coupling with Workers API, and instead, we suggest encapsulating them in a domain-specific API to simplify future migration and reduce potential exposure to dangerous API.