@brightcove/components-embed-code-modal 0.1.24 → 0.1.26

package/README.md

@@ -17,7 +17,13 @@ npm install
 npm run demo
 ```
 
-This will open a browser tab on `localhost:8080` with a sandbox
+Sign in to Studio with a Studio UI (Marketing Studio) enabled account. If necessary, click the Profile icon and then the Switch to Studio link.
+
+Navigate to [https://studio.brightcove.com/products/videocloud/media/dev/sdk:remote](https://studio.brightcove.com/products/videocloud/media/dev/sdk:remote).
+
+The App runs at [https://localhost.brightcove.com:12345/js/app.js](https://localhost.brightcove.com:12345/js/app.js) as described in [Creating a Module](https://brightcove.atlassian.net/wiki/spaces/APPS/pages/2287471973/Creating+A+Module#How-does-that-dev%2Fsdk%3Aremote-URL-work%3F)
+
+The results of the API call to retrieve players will depend on sign in permissions.
 
 ## Integrating with modules
 
@@ -91,12 +97,12 @@ const handleAction = (event: DataGridAction) => {
 };
 ```
 
-1) The Media Module imports both the `DataGrid` & `EmbedCodeModal` components. Neither component are coded to be aware of the other.
-2) The `DataGrid` component dispatches the `GetCode` action to tell its parent module: *I would like to retrieve some code, go and do that, however your module handles this action*.
-3) The Media Module handles this action by creating a new payload with the video information handed off by the DataGrid. It knows that it wants to open the EmbedCodeModal, so it will look to the `VideoPayload` interface to create what it needs.
-4) This video object is set to the module's local state.
-5) Within our JSX, our EmbedCodeModal should be passing this video object to the component: `<EmbedCodeModal video={embedVideo} />`
-6) Anytime that `embedVideo` updates in the module - it triggers the Embed Code Modal to open.
+1. The Media Module imports both the `DataGrid` & `EmbedCodeModal` components. Neither component are coded to be aware of the other.
+2. The `DataGrid` component dispatches the `GetCode` action to tell its parent module: _I would like to retrieve some code, go and do that, however your module handles this action_.
+3. The Media Module handles this action by creating a new payload with the video information handed off by the DataGrid. It knows that it wants to open the EmbedCodeModal, so it will look to the `VideoPayload` interface to create what it needs.
+4. This video object is set to the module's local state.
+5. Within our JSX, our EmbedCodeModal should be passing this video object to the component: `<EmbedCodeModal video={embedVideo} />`
+6. Anytime that `embedVideo` updates in the module - it triggers the Embed Code Modal to open.
 
 The reasons we have wired things up this way has been to achieve our goals of keeping micro-frontends decoupled. The EmbedCodeModal & the DataGrid are not interacting directly with each other. The DataGrid is providing video data that is being used, but when it triggers a `Get Code` event, it can just send an entire Video Object along with it. It doesn't need to know exactly what information the Embed Code Modal needs in order to successfully operate.
 

package/__tests__/InteractivityProject.test.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=InteractivityProject.test.d.ts.map

package/__tests__/InteractivityProject.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"InteractivityProject.test.d.ts","sourceRoot":"","sources":["../../__tests__/InteractivityProject.test.tsx"],"names":[],"mappings":""}