Repository navigation
feat!: adopt TS generator changes - #1896
Conversation
szuperaz
changed the title
| unban?: UnbanActionRequestPayload; | ||
| /** | ||
| * Deprecated: use restore instead — it now also reverses a block or shadow block. Configuration for unblock action. | ||
| * @deprecated |
There was a problem hiding this comment.
As we are working on major version, would it make sense to remove the deprecated properties?
There was a problem hiding this comment.
Hm, this is a good question. The open api generator doesn't exclude deprecated properties; this is because deprecations can happen at any time. If they're removed from the backend, they will be removed from the generated code too; but since the backend can't really have breaking changes, they probably won't remove deprecated fields. We may want to solve this down the road for generated SDKs (as this affects all SDKs), but since for JS we're wrapping up work before this major, it won't be this release.
There was a problem hiding this comment.
I've checked and we have 5 fields currently in generated models, and this number shouldn't really grow ideally, because it's quite rare that we depreacte a field in backend, exactly because we can't really do breaking changes there.
## [10.0.0-rc.18](v10.0.0-rc.17...v10.0.0-rc.18) (2026-10-05) ### ⚠ BREAKING CHANGES * adopt TS generator changes (#1896) ### Bug Fixes * set thread cursor when initied from setItems ([#1898](#1898)) ([63bef43](63bef43)) ### Features * adopt TS generator changes ([#1896](#1896)) ([82af6de](82af6de))
|
🎉 This PR is included in version 10.0.0-rc.18 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Relevant strema-chat-js PR: GetStream/stream-chat-js#1896 https://linear.app/stream/issue/REACT-1189/reduce-bundle-size-change-api-signature ## 🎯 Goal <!-- Describe why we are making this change --> ## 🛠 Implementation details <!-- Provide a description of the implementation --> ## 🎨 UI Changes <!-- Add relevant screenshots --> <details> <summary>iOS</summary> <table> <thead> <tr> <td>Before</td> <td>After</td> </tr> </thead> <tbody> <tr> <td> <!--<img src="" /> --> </td> <td> <!--<img src="" /> --> </td> </tr> </tbody> </table> </details> <details> <summary>Android</summary> <table> <thead> <tr> <td>Before</td> <td>After</td> </tr> </thead> <tbody> <tr> <td> <!--<img src="" /> --> </td> <td> <!--<img src="" /> --> </td> </tr> </tbody> </table> </details> ## 🧪 Testing <!-- Explain how this change can be tested (or why it can't be tested) --> ## ☑️ Checklist - [ ] I have signed the [Stream CLA](https://docs.google.com/forms/d/e/1FAIpQLScFKsKkAJI7mhCr7K9rEIOpqIDThrWxuvxnwUq2XkHyG154vQ/viewform) (required) - [ ] PR targets the `develop` branch - [ ] Documentation is updated - [ ] New code is tested in main example apps, including all possible scenarios - [ ] SampleApp iOS and Android - [ ] Expo iOS and Android
5 participants
Breaking changes
requestparam to avoid future changes.https://linear.app/stream/issue/REACT-1189/reduce-bundle-size-change-api-signature
https://linear.app/stream/issue/REACT-1205/ts-generator-avoid-potential-breaking-change-when-using-with-request
Description of the changes, What, Why and How?
ReminderPaginatorsent wrong key for pagination, this is now fixedrequestOptionsshould always be the last param of an API call, we can cause a breaking change if an API call that doesn't have query/body params today, gets new params because that would shiftrequestOptionsarg position. To fix this issue we add a placeholder param to all API calls: