Repository navigation
chore(legacy)!: remove legacy API support and WebRTC - #1589
Conversation
|
@barhanc Do we want to merge this one pretty much immediately or right before the v1.0.0 release? If we want to do it now, then potential patches for v0.11.x will be stripped from the legacy part, while v0.11.0 will have it. |
|
We don't have to cherry-pick the commit with this change when releasing the patch versions so they keep the legacy path. I would merge this as early as possible, so that we work on the lib structure that is the target one. |
Fair enough. I'm checking this rn. You can handle the conflict in the meantime ;) |
|
Ok, I've completed full passes over all demo apps on android and iOS (both real devices and simulators) and everything seemed to worked correctly. Now the docs pass and we are good to go. |
Description
Removes the legacy API, example apps, resource fetcher packages, WebRTC package, and legacy documentation. Cleans up native bindings, build configuration, publishing workflows, dependencies, and tests.
Introduces a breaking change?
Type of change
Tested on
Testing instructions
Screenshots
Related issues
Closes #1421
Checklist
Additional notes