You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -321,6 +321,7 @@
321
321
|305|[What is the stable release for hooks support?](#what-is-the-stable-release-for-hooks-support)|
322
322
|306|[Why do we use square brackets in useState?](#why-do-we-use-square-brackets-in-usestate?)|
323
323
|307|[What are the sources used for introducing hooks?](#what-are-the-sources-used-for-introducing-hooks)|
324
+
|308|[How do you access imperative API of web components?](#how-do-you-access-imperative-api-of-web-components)|
324
325
325
326
## Core React
326
327
@@ -5088,4 +5089,6 @@
5088
5089
2. Community experiments with render prop APIs such as Reactions Component
5089
5090
3. State variables and state cells in DisplayScript.
5090
5091
4. Subscriptions in Rx.
5091
-
5. Reducer components in ReasonReact.
5092
+
5. Reducer components in ReasonReact.
5093
+
308. ### How do you access imperative API of web components?
5094
+
Web Components often expose an imperative API to implement its functions. You will need to use a **ref** to interact with the DOM node directly if you want to access imperative API of a web component. But if you are using third-party Web Components, the best solution is to write a React component that behaves as a **wrapper** for your Web Component.
0 commit comments