@prismatic-io/spectral 10.3.1 → 10.3.3

package/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2020 Prismatic LLC.
+Copyright (c) 2024 Prismatic LLC.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -1,6 +1,9 @@
-# @prismatic-io/spectral
+<div align="center">
+  <img src="https://prismatic.io/favicon-48x48.png" />
+  <h1>@prismatic-io/spectral</h1>
+</div>
 
-This repository contains code for Prismatic's TypeScript library, `spectral`, which is used to build custom Prismatic components.
+This repository contains code for Prismatic's TypeScript library, `spectral`, which is used to build custom Prismatic connectors and code-native integrations.
 
 ## Using Spectral
 
@@ -10,47 +13,41 @@ To install spectral, run:
 npm install @prismatic-io/spectral
 ```
 
-Please see our [documentation](https://prismatic.io/docs/custom-components/writing-custom-components) on writing and publishing custom components for Prismatic's platform.
+Please see our [documentation](https://prismatic.io/docs/custom-connectors/) on writing and publishing custom connectors for Prismatic's platform.
 
 ## What is Prismatic?
 
-Prismatic is the integration platform for B2B software companies. It's the quickest way to build integrations to the other apps your customers use and to add a native integration marketplace to your product.
+Prismatic is the leading embedded iPaaS, enabling B2B SaaS teams to ship product integrations faster and with less dev time. The only embedded iPaaS that empowers both developers and non-developers with tools for the complete integration lifecycle, Prismatic includes low-code and code-native building options, deployment and management tooling, and self-serve customer tools.
 
-Prismatic significantly reduces overall integration effort and enables non-dev teams to take on more of the integration workload, so that you can deliver integrations faster and spend more time on core product innovation.
+Prismatic's unparalleled versatility lets teams deliver any integration from simple to complex in one powerful platform. SaaS companies worldwide, from startups to Fortune 500s, trust Prismatic to help connect their products to the other products their customers use.
 
 With Prismatic, you can:
 
-- Build reusable [integrations](https://prismatic.io/docs/integrations) in a low-code integration designer that's tailored for your product
-- Use [pre-built components](https://prismatic.io/docs/components/component-catalog) to handle most of your integrations' functionality, and write [custom components](https://prismatic.io/docs/custom-components/writing-custom-components) when needed
-- Quickly add an [integration marketplace](https://prismatic.io/docs/integration-marketplace) to your product so customers can explore, activate, and monitor integrations
-- Easily deploy customer-specific integration [instances](https://prismatic.io/docs/instances) with unique configurations and connections
-- Provide better support with tools like [logging](https://prismatic.io/docs/logging) and [alerting](https://prismatic.io/docs/monitoring-and-alerting)
-- Run your integrations in a purpose-built environment designed for security and scalability
-- Use powerful dev tools to mold the platform to your product, industry, and the way you build software
+- Build [integrations](https://prismatic.io/docs/integrations/) using our [intuitive low-code designer](https://prismatic.io/docs/integrations/low-code-integration-designer/) or [code-native](https://prismatic.io/docs/integrations/code-native/) approach in your preferred IDE
+- Leverage pre-built [connectors](https://prismatic.io/docs/components/) for common integration tasks, or develop custom connectors using our TypeScript SDK
+- Embed a native [integration marketplace](https://prismatic.io/docs/embed/) in your product for customer self-service
+- Configure and deploy customer-specific integration instances with powerful configuration tools
+- Support customers efficiently with comprehensive [logging, monitoring, and alerting](https://prismatic.io/docs/monitor-instances/)
+- Run integrations in a secure, scalable infrastructure designed for B2B SaaS
+- Customize the platform to fit your product, industry, and development workflows
 
 ## Who uses Prismatic?
 
-Prismatic is for B2B (business-to-business) software companies, meaning software companies that provide applications used by businesses. It's a good fit for products/teams ranging from early-stage and growing SaaS startups to large, established software companies looking to improve the way they do integrations.
+Prismatic is built for B2B software companies that need to provide integrations to their customers. Whether you're a growing SaaS startup or an established enterprise, Prismatic's platform scales with your integration needs.
 
-Many B2B software teams serve customers in niche vertical markets, and we designed Prismatic with that in mind. We provide powerful and flexible tools so you can build exactly the integrations your customers need, no matter who your customers are, no matter what systems you need to connect to, no matter how "non-standard" your integration scenario.
+Our platform is particularly powerful for teams serving specialized vertical markets. We provide the flexibility and tools to build exactly the integrations your customers need, regardless of the systems you're connecting to or how unique your integration requirements may be.
 
 ## What kind of integrations can you build using Prismatic?
 
-Prismatic supports integrations ranging from simple and standard to complex, bespoke, and vertical-specific.
-Teams use it to build integrations between applications of all kinds, SaaS or legacy, with or without a modern API, regardless of protocol or data format.
-Here are some example use cases:
+Prismatic supports integrations of any complexity - from simple data syncs to sophisticated, industry-specific solutions. Teams use it to build integrations between any type of system, whether modern SaaS or legacy with standard or custom protocols. Here are some example use cases:
 
-- Use job data from your system to create invoices in your customers' ERP.
-- Import and process data from third-party forms that vary significantly from customer to customer.
-- Email activity summary reports with parameters and intervals defined on a per-customer basis.
+- Connect your product with customers' ERPs, CRMs, and other business systems
+- Process data from multiple sources with customer-specific transformation requirements
+- Automate workflows with customizable triggers, actions, and schedules
+- Handle complex authentication flows and data mapping scenarios
 
-For information on the Prismatic platform, check out our [website](https://prismatic.io) and [docs](https://prismatic.io/docs).
-
-## Building Spectral Locally
-
-To build spectral locally, you'll need `yarn` and `node` installed.
-Run `yarn build` to build the package, or `yarn pack` to build a tarball that can be used in custom components for testing changes to spectral.
+For information on the Prismatic platform, check out our [website](https://prismatic.io/) and [docs](https://prismatic.io/docs/).
 
 ## License
 
-This repository is [MIT licensed](./LICENSE).
+This repository is MIT licensed.

package/dist/serverTypes/perform.js

@@ -46,7 +46,7 @@ const createInvokeFlow = (context, options = {}) => {
     return (flowName, data, config, source) => __awaiter(void 0, void 0, void 0, function* () {
         var _a;
         const sourceToUse = options.isCNI ? source : undefined;
-        return yield axios_1.default.post(context.webhookUrls[flowName], data, Object.assign(Object.assign({}, config), { headers: Object.assign(Object.assign({}, ((_a = config === null || config === void 0 ? void 0 : config.headers) !== null && _a !== void 0 ? _a : {})), { "prismatic-invoked-by": formatExecutionFrameHeaders(context.executionFrame, sourceToUse) }) }));
+        return yield axios_1.default.post(context.webhookUrls[flowName], data, Object.assign(Object.assign({}, config), { headers: Object.assign(Object.assign({}, ((_a = config === null || config === void 0 ? void 0 : config.headers) !== null && _a !== void 0 ? _a : {})), { "prismatic-invoked-by": formatExecutionFrameHeaders(context.executionFrame, sourceToUse), "prismatic-invoke-type": "Cross Flow" }) }));
     });
 };
 exports.createInvokeFlow = createInvokeFlow;

package/dist/testing.d.ts

@@ -4,8 +4,8 @@
  * information on unit testing, check out our docs:
  * https://prismatic.io/docs/custom-components/writing-custom-components/#testing-a-component
  */
-import { TriggerPayload, TriggerResult, ConnectionValue, ActionLogger, Component, ActionPerformReturn, DataSourceResult, DataSourceContext } from "./serverTypes";
-import { ActionContext, ConnectionDefinition, ActionDefinition, TriggerDefinition, Inputs, ActionInputParameters, DataSourceDefinition, ActionPerformReturn as InvokeActionPerformReturn, TriggerResult as InvokeTriggerResult, DataSourceType, DataSourceResult as InvokeDataSourceResult, TriggerEventFunctionReturn, Flow, ConfigVarResultCollection } from "./types";
+import { ActionPerformReturn as ServerActionPerformReturn, TriggerPayload, TriggerResult, ConnectionValue, ActionLogger, Component, DataSourceResult, DataSourceContext } from "./serverTypes";
+import { ActionContext, ConnectionDefinition, ActionDefinition, TriggerDefinition, Inputs, ActionInputParameters, DataSourceDefinition, ActionPerformReturn as InvokeActionPerformReturn, TriggerResult as InvokeTriggerResult, DataSourceType, DataSourceResult as InvokeDataSourceResult, TriggerEventFunctionReturn, Flow, ConfigVarResultCollection, ComponentManifest } from "./types";
 export declare const createConnection: <T extends ConnectionDefinition>({ key }: T, values: Record<string, unknown>, tokenValues?: Record<string, unknown>) => ConnectionValue;
 export declare const defaultConnectionValueEnvironmentVariable = "PRISMATIC_CONNECTION_VALUE";
 export declare const connectionValue: (envVarKey?: string) => ConnectionValue;
@@ -14,6 +14,23 @@ export declare const connectionValue: (envVarKey?: string) => ConnectionValue;
  * See https://prismatic.io/docs/custom-components/writing-custom-components/#verifying-correct-logging-in-action-tests for information on testing correct logging behavior in your custom component.
  */
 export declare const loggerMock: () => ActionLogger;
+/**
+ * Creates basic component mocks based on the CNI's component registry.
+ * You may pass mock overrides in the second argument, e.g.:
+ *
+ * createMockContextComponents(myManifest, {
+ *   actions: {
+ *     myComponentName: {
+ *        myComponentAction: () => Promise.resolve({ data: "my test data "}),
+ *     }
+ *   },
+ * });
+ */
+export declare const createMockContextComponents: <TMockAction extends () => Promise<any>>(registry: Record<string, {
+    actions: ComponentManifest["actions"];
+}>, mocks?: {
+    actions: Record<string, Record<string, TMockAction>>;
+}) => Record<string, Record<string, TMockAction>>;
 /**
  * The type of data returned by an `invoke()` function used for unit testing component actions and triggers.
  */
@@ -64,7 +81,7 @@ export declare class ComponentTestHarness<TComponent extends Component> {
     trigger<TConfigVars extends ConfigVarResultCollection>(key: string, payload?: TriggerPayload, params?: Record<string, unknown>, context?: Partial<ActionContext<TConfigVars>>): Promise<TriggerResult>;
     triggerOnInstanceDeploy<TConfigVars extends ConfigVarResultCollection>(key: string, params?: Record<string, unknown>, context?: Partial<ActionContext<TConfigVars>>): Promise<TriggerEventFunctionReturn | void>;
     triggerOnInstanceDelete<TConfigVars extends ConfigVarResultCollection>(key: string, params?: Record<string, unknown>, context?: Partial<ActionContext<TConfigVars>>): Promise<TriggerEventFunctionReturn | void>;
-    action<TConfigVars extends ConfigVarResultCollection>(key: string, params?: Record<string, unknown>, context?: Partial<ActionContext<TConfigVars>>): Promise<ActionPerformReturn>;
+    action<TConfigVars extends ConfigVarResultCollection>(key: string, params?: Record<string, unknown>, context?: Partial<ActionContext<TConfigVars>>): Promise<ServerActionPerformReturn>;
     dataSource<TConfigVars extends ConfigVarResultCollection>(key: string, params?: Record<string, unknown>, context?: Partial<DataSourceContext<TConfigVars>>): Promise<DataSourceResult>;
 }
 export declare const createHarness: <TComponent extends Component>(component: TComponent) => ComponentTestHarness<TComponent>;

package/dist/testing.js

@@ -15,7 +15,7 @@ var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, ge
     });
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.createHarness = exports.ComponentTestHarness = exports.invokeFlow = exports.invokeDataSource = exports.invokeTrigger = exports.defaultTriggerPayload = exports.invoke = exports.loggerMock = exports.connectionValue = exports.defaultConnectionValueEnvironmentVariable = exports.createConnection = void 0;
+exports.createHarness = exports.ComponentTestHarness = exports.invokeFlow = exports.invokeDataSource = exports.invokeTrigger = exports.defaultTriggerPayload = exports.invoke = exports.createMockContextComponents = exports.loggerMock = exports.connectionValue = exports.defaultConnectionValueEnvironmentVariable = exports.createConnection = void 0;
 const jest_mock_1 = require("jest-mock");
 const createConnection = ({ key }, values, tokenValues) => ({
     configVarKey: "",
@@ -53,6 +53,33 @@ function invokeFlowTest(flowName, data, config) {
         return Promise.resolve({});
     });
 }
+/**
+ * Creates basic component mocks based on the CNI's component registry.
+ * You may pass mock overrides in the second argument, e.g.:
+ *
+ * createMockContextComponents(myManifest, {
+ *   actions: {
+ *     myComponentName: {
+ *        myComponentAction: () => Promise.resolve({ data: "my test data "}),
+ *     }
+ *   },
+ * });
+ */
+const createMockContextComponents = (registry, mocks = { actions: {} }) => {
+    const components = Object.keys(registry).reduce((accum, componentKey) => {
+        var _a;
+        const mockActions = Object.keys(registry[componentKey].actions).reduce((actionAccum, actionKey) => {
+            actionAccum[actionKey] = (() => {
+                return Promise.resolve({ data: null });
+            });
+            return actionAccum;
+        }, {});
+        accum[componentKey] = Object.assign(Object.assign({}, mockActions), ((_a = mocks.actions[componentKey]) !== null && _a !== void 0 ? _a : {}));
+        return accum;
+    }, {});
+    return components;
+};
+exports.createMockContextComponents = createMockContextComponents;
 const createActionContext = (context) => {
     return Object.assign({ logger: (0, exports.loggerMock)(), instanceState: {}, crossFlowState: {}, executionState: {}, integrationState: {}, configVars: {}, components: {}, stepId: "mockStepId", executionId: "mockExecutionId", webhookUrls: {
             "Flow 1": "https://example.com",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@prismatic-io/spectral",
-  "version": "10.3.1",
-  "description": "Utility library for building Prismatic components and code-native integrations",
+  "version": "10.3.3",
+  "description": "Utility library for building Prismatic connectors and code-native integrations",
   "keywords": ["prismatic"],
   "main": "dist/index.js",
   "types": "dist/index.d.ts",