@integry/sdk 4.7.39 → 4.7.41

package/package.json

@@ -1,10 +1,15 @@
 {
   "name": "@integry/sdk",
-  "version": "4.7.39",
+  "version": "4.7.41",
   "description": "Integry SDK",
   "main": "dist/umd/index.umd.js",
   "module": "dist/esm/index.csm.js",
   "types": "dist/esm/index.csm.d.ts",
+  "files": [
+    "dist",
+    "README.md",
+    "LICENSE"
+  ],
   "scripts": {
     "bump": "bump -t \"sdk-release-v%s\" -c \"SDK release v%s\"",
     "lint": "eslint src --ext .js --ext .ts",

package/.eslintignore

@@ -1 +0,0 @@
-**/*.test.ts

package/.vscode/launch.json

@@ -1,17 +0,0 @@
-{
-  // Use IntelliSense to learn about possible attributes.
-  // Hover to view descriptions of existing attributes.
-  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "type": "chrome",
-      "request": "launch",
-      "name": "Open Integry SDK sample code (44).html",
-      // "file": "/Users/yasir/Downloads/Flows - Integry SDK sample (41).html"
-      "file": "/Users/yasir/Downloads/Integry SDK sample code (73).html"
-      // "file": "/Users/yasir/Downloads/Flows of an app - Integry SDK sample (Thryv 7) For All (2).html"
-      // "file": "/Users/yasir/Downloads/Integry SDK sample code (64).html"
-    }
-  ]
-}

package/CHANGELOG_INTERNAL.md

@@ -1,134 +0,0 @@
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-
-## [3.9.1] - 2023-10-24
-
-## Fixed
-
-- Fixed the search not working properly for flows listing.
-
-## [3.9.0] - 2023-10-24
-
-## Changed
-
-- Changed the sequence of flow setup form to show all connect screens first.
-
-## [3.7.18] - 2023-10-04
-
-## Added
-
-- Added loading spinner while deleting an integration from "flows of an app" view.
-
-## [3.7.16] - 2023-10-03
-
-## Added
-
-- Added feature to allow deleting an integration from "flows of an app" view.
-
-## [3.7.15] - 2023-09-28
-
-## Changed
-
-- Rebrand Instance as Integrations on flow list screen.
-
-## [3.7.14] - 2023-09-26
-
-## Added
-
-- Add App icon in "All Flows" view of SDK.
-
-## [3.7.12] - 2023-09-20
-
-## Changed
-
-- Show host app step when API key is not provided in SDK config.
-
-## [3.7.11] - 2023-09-19
-
-## Added
-
-- Added `options` object to pass SDK options like `tags` and `title`.
-
-## [3.7.10] - 2023-09-19
-
-## Changed
-
-- `title` field will be used to set title of all SDK views.
-
-## [3.7.7] - 2023-09-19
-
-## Fixed
-
-- Minor bug fixes
-
-## [3.7.7] - 2023-09-19
-
-### Added
-
-- Added support for deployment ID for legacy users. When a deployment ID is provided to the SDK, only `Published` flows will be listed.
-
-## [3.7.6] - 2023-09-18
-
-### Changed
-
-- Updated SDK button color to Integry blue.
-
-## [3.7.4] - 2023-09-18
-
-### Changed
-
-- Made deployment ID optional in SDK config.
-
-## [3.7.2] - 2023-09-18
-
-### Added
-
-- Refreshed SDK when authorization is deleted using the `removeAuthorization` function.
-
-## [3.7.1] - 2023-09-14
-
-### Added
-
-- Added 'did-app-load' event when App loading is completed.
-
-## [3.6.9] - 2023-09-15
-
-### Added
-
-- Added a function called `removeAuthorization` to delete end-user authorization.
-
-## [3.6.7] - 2023-09-09
-
-### Changed
-
-- Changed button label to "Setup" for "Save and Execute Later" On-Demand Flow.
-
-## [3.6.3] - 2023-09-08
-
-### Fixed
-
-- Hidden Tooltip on Flow setup button after account verification is completed.
-
-## [3.6.2] - 2023-09-08
-
-### Added
-
-- Added support to execute On-Demand Flow on save if Flow is configured as "Save and Execute."
-- Objects passed in SDK configuration will be used as a payload when executing On-Demand Flow.
-
-## [3.6.1] - 2023-09-08
-
-### Fixed
-
-- Minor UI Fixes.
-
-## [3.6.0] - 2023-09-07
-
-### Added
-
-- Added support for SDK to accept Objects in SDK configuration for Incoming Webhook. These Objects will be used for field mapping.

package/README_INTERNAL.md

@@ -1,176 +0,0 @@
-# Integry SDK
-
-## General features
-
-- No extra dependencies needed, drastically reduced bundle size
-- No transpilation steps needed
-- Vanilla JS implementation
-- Improved documentation
-- Available as a package on NPM
-- Can be embedded using a script tag
-- Built-in Typescript support
-- More powerful events management
-- Multi-level customization. Start with built in components and layouts.
-- Multiple render modes including inline rendering, modal support and detached rendering where we decouple the views from one another
-- Discover more customization options starting from simple CSS overrides to extending and implementing your own custom widgets
-
-## Tech stack
-
-- [Preact](https://github.com/developit/preact)
-- [htm](https://github.com/developit/htm)
-- [Unistore](https://github.com/developit/unistore)
-- [Rollup](https://rollupjs.org/)
-- NodeJS
-- Yarn
-
-## Directory structure
-
-```
-.
-├── dist                   # Compiled files
-├── examples               # Example projects using SDK
-├── playground             # HTML files covering different debug scenarios
-├── sdk-docs               # `Docusaurus` documentation site for SDK
-├── src                    # Source files
-│   ├── components         # Preact components used in the SDK
-│   ├── contexts           # Preact contexts used in the SDK
-│   ├── extensions         # SDK HMAC and API extensions
-│   ├── features           # Directory-wise breakdown of different SDK views
-│   ├── hooks              # Preact hooks
-│   ├── interfaces         # Typescript interfaces
-│   ├── modules            # API and event emitter live here
-│   ├── store              # SDK data store setup
-│   ├── types              # Typescript types live here
-│   ├── utils              # Utilities used in the SDK
-│   ├── index.ts           # JS Modules entry point
-│   └── index.umd.ts       # UMD entry point
-├── types                  # General Typescript types for rollup
-├── rollup.config.js       # Rollup configuration
-├── tsconfig.json          # TS configuration
-└── README.md
-```
-
-## Setting up your development environment
-
-### Pre-requisites
-
-1. NodeJS
-2. yarn
-
-### Starting the local environment
-
-1. `cd` into the SDK root directory which is located at `<repo_root>/sdk-v3`
-2. Install dependencies by running `yarn install`
-3. Start the local development environment by running `yarn start`
-4. The development server will start at http://localhost:10001
-
-### Choosing which mode to debug
-
-The SDK has multiple playground HTML files to work on different areas. Each html file lives in the `sdk-v3/playground` directory and contains code which sets up the SDK and calls different methods. You can edit these files to debug different aspects of the SDK.
-
-1. http://localhost:10001/index.html
-
-You can use this playground to debug a normal SDK embed which starts from the Flows listing page. You can click on a Flow and setup integrations. You can select from the tabs at the top to either view available Flows or view existing integrations.
-
-2. http://localhost:10001/template.html
-
-You can use this playground to directly open a Flow.
-
-3. http://localhost:10001/auths.html
-
-You can use this playground to work on the app account management feature provided by the SDK.
-
-## Development
-
-### Hot reloading
-
-When you make a change to the code in development mode, Rollup will automatically re-compile the code. After it is done, you will have to refresh the page to see the latest changes.
-
-### Debugging using Redux Devtools
-
-The SDK supports Redux Devtools to look into the internal state and debug actions. Devtools are enabled by default and can be enabled/disabled in the `src/store/index.ts` file. To use the devtools, install the Redux Devtools extension, open the developer tools in your browser and then refresh the SDK playground page.
-
-### Styling
-
-Styles are co-located with each component in a `styles.module.scss` file. This is then imported into a component and used.
-
-```tsx
-import styles from './styles.module.scss';
-
-<div class=${styles.selectWrapper} />
-```
-
-## Debugging certain features
-
-### API Calls
-
-All API calls are centrally located inside the directory: `src/modules/api/index.ts`.
-
-### Manage app accounts
-
-The code for the manage app accounts feature starts with the `index.ts` entry point.
-
-```ts
-  /**
-   * Render the account connection modal
-   * @param data
-   */
-  public renderAccountConnectionModal = (data?: {
-    deploymentId?: string;
-    appId?: number;
-    authTypeId?: number;
-  }): void => {
-    //
-  }
-```
-
-This function sets up our render destination inside the HTML, initializes the store and finally calls the Preact `render` method to render the `AuthSetupContainer` component inside the target container.
-
-All of the code for managing app accounts feature is located in `src/features/containers/AuthSetupContainer`.
-
-```
-. AuthSetupContainer
-├── AppSelection.ts           # Renders the app selection screen
-├── AuthTypeSelection.ts      # Renders the auth type selection screen
-├── Footer.ts                 # Renders the footer inside auth type selection
-├── Header.ts                 # Renders the header which shows step title and close icon
-├── index.ts                  # Wraps the entire feature with state and API calls
-└── PostAdditionPopup.ts      # Renders the modal which appears after we add an auth
-```
-
-### Flow setup
-
-The code for flow setup starts with the `index.ts` entry point.
-
-```ts
-  /**
-   * Render the flow setup form we ship
-   * @param data
-   */
-  public renderFlowSetupForm = (data: {
-    flowId?: string;
-    flowContainerId: string;
-  }): void => {
-    //
-  }
-```
-
-This function sets up our render destination inside the HTML, initializes the store and finally calls the Preact `render` method to render the `FlowSetupContainer` component inside the target container.
-
-All of the code for rendering a Flow setup form is located in `src/features/containers/FlowSetupContainer/index.ts`.
-
-### Normal SDK embed
-
-The code for the normal SDK embed setup starts with the `index.ts` entry point.
-
-```ts
-  /**
-   *
-   * @param initConfig
-   */
-  public init = (initConfig: InitConfig) => {}
-```
-
-This function sets up our render destination inside the HTML, initializes the store and finally calls the Preact `render` method to render the `SDKContainer` component inside the target container.
-
-All of the code for rendering a the normal SDK embed is located in `src/features/containers/SDKContainer/index.ts`.