-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
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
fix(TU-15133): Rename ref
prop to embedRef
for proper typing
#657
Conversation
6a42cd8
to
5318a9c
Compare
1f898a8
to
c2d16e5
Compare
TypeScript adoptionCurrent adoption level: 96.4% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, it looks good, just a small comment n the tests, that were added an only
.
BREAKING CHANGE: Components are unable to access `ref` prop directly. Using `forwardRef` breaks the typings. Since we do not accept any `ForwardedRef` but rather only `MutableRefObject`, we will rename the prop to type it correctly.
Add examples for the App Router available from NextJS version >= 13.
BREAKING CHANGE: The library no longer supports node version 16 (end of life 2023-09-11). React version is bumped and requires node >= 18.
[BOT] Preview available with hash |
# [@typeform/embed-v5.0.0](https://github.com/Typeform/embed/compare/@typeform/embed-v4.10.3...@typeform/embed-v5.0.0) (2024-07-17) ### Bug Fixes * **TU-15133:** Rename `ref` prop to `embedRef` for proper typing ([#657](#657)) ([7860e94](7860e94)) ### BREAKING CHANGES * **TU-15133:** Components are unable to access `ref` prop directly. Using `forwardRef` breaks the typings. Since we do not accept any `ForwardedRef` but rather only `MutableRefObject`, we will rename the prop to type it correctly. * chore(TU-15133): Update NextJS demos to run on latest version Add examples for the App Router available from NextJS version >= 13. * feat(TU-15133): Update CI to run on Node version 22 * **TU-15133:** The library no longer supports node version 16 (end of life 2023-09-11). React version is bumped and requires node >= 18.
🎉 This PR is included in version @typeform/embed-v5.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
# [@typeform/embed-react-v4.0.0](https://github.com/Typeform/embed/compare/@typeform/embed-react-v3.20.0...@typeform/embed-react-v4.0.0) (2024-07-17) ### Bug Fixes * **TU-15133:** Rename `ref` prop to `embedRef` for proper typing ([#657](#657)) ([7860e94](7860e94)) ### Features * Bump @typeform/embed in @typeform/embed-react package [skip ci] ([b2ada39](b2ada39)) ### BREAKING CHANGES * **TU-15133:** Components are unable to access `ref` prop directly. Using `forwardRef` breaks the typings. Since we do not accept any `ForwardedRef` but rather only `MutableRefObject`, we will rename the prop to type it correctly. * chore(TU-15133): Update NextJS demos to run on latest version Add examples for the App Router available from NextJS version >= 13. * feat(TU-15133): Update CI to run on Node version 22 * **TU-15133:** The library no longer supports node version 16 (end of life 2023-09-11). React version is bumped and requires node >= 18.
🎉 This PR is included in version @typeform/embed-react-v4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Changes:
ref
prop directly. UsingforwardRef
breaks the typings. Since we do not accept anyForwardedRef
but rather onlyMutableRefObject
, we will rename the prop to type it correctly.BREAKING CHANGES:
ref
toembedRef
in order to type it properly