@newsletterstudio/umbraco 14.0.0-rc1 → 14.0.4

package/dist/backend-api/types.gen.d.ts

@@ -474,6 +474,24 @@ export type ImageEmailControlDataModel = {
      */
     aspectRatio: string;
 };
+export type ImportFixedIssueRequestFrontendModel = {
+    recipient: ImportRecipientIssuesFrontendModel;
+    mailingListKey?: string | null;
+    workspaceKey?: string | null;
+    fieldMappings: Array<ImportRecipientsColumnMappingFieldValueFrontendModel>;
+    /**
+     * Indicates if the import should overwrite data if the recipient already exists
+     */
+    updateExisting: boolean;
+};
+export type ImportRecipientIssuesFrontendModel = {
+    email: string;
+    firstname: string;
+    lastname: string;
+    fields: {
+        [key: string]: string;
+    };
+};
 export type ImportRecipientIssuesValueFrontendModel = {
     email: string;
     firstname: string;
@@ -522,6 +540,10 @@ export type ImportRecipientsPerformFileImportRequestFrontendModel = {
     mailingListKey?: string | null;
     tempFile: string;
     fieldMappings: Array<ImportRecipientsColumnMappingFieldValueFrontendModel>;
+    /**
+     * Indicates if the import should overwrite data if the recipient already exists
+     */
+    updateExisting: boolean;
 };
 export type ImportRecipientsResultsResponseFrontendModel = {
     total: number;
@@ -1565,7 +1587,7 @@ export type EmailEditorGetMacrosData = {
 };
 export type EmailEditorGetMacrosResponse = Array<ListItemIdAndLabelValueFrontendModel>;
 export type ImportRecipientsImportFixedIssueData = {
-    requestBody?: ImportRecipientIssuesValueFrontendModel;
+    requestBody?: ImportFixedIssueRequestFrontendModel;
 };
 export type ImportRecipientsImportFixedIssueResponse = Array<number>;
 export type ImportRecipientsPerformFileImportData = {

package/dist/core/components/ns-checkbox/ns-checkbox.element.d.ts

@@ -23,11 +23,13 @@ export declare class NsCheckboxElement extends LitElement {
     */
     label: string;
     disabled: boolean;
+    description: string;
     _input: HTMLInputElement;
     connectedCallback(): Promise<void>;
     disconnectedCallback(): void;
     _handleChange(e: InputEvent): void;
     render(): import("lit-html").TemplateResult<1>;
+    renderLabel(): import("lit-html").TemplateResult<1>;
     static styles: import("lit").CSSResult[];
 }
 declare global {

package/dist/core/components/ns-timeline/ns-timeline-event.element.d.ts

@@ -1,7 +1,7 @@
 import { UmbLitElement } from '@umbraco-cms/backoffice/lit-element';
 import '@newsletterstudio/umbraco/components';
 import './ns-timeline-icon.element.js';
-export type NsTimelineEventType = undefined | 'default' | 'campaign-delivered' | 'campaign-opened' | 'campaign-clicked' | 'campaign-view-in-browser' | 'campaign-delivery-error' | 'mailinglist-subscribed' | 'mailinglist-unsubscribed' | 'recipient-added' | 'transactional-delivered' | 'transactional-opened' | 'transactional-clicked' | 'transactional-error';
+export type NsTimelineEventType = undefined | 'default' | 'campaign-delivered' | 'campaign-opened' | 'campaign-clicked' | 'campaign-view-in-browser' | 'campaign-delivery-error' | 'campaign-unsubscribe-performed' | 'mailinglist-subscribed' | 'mailinglist-unsubscribed' | 'recipient-added' | 'transactional-delivered' | 'transactional-opened' | 'transactional-clicked' | 'transactional-error';
 /**
 * ns-timeline-event
 */

package/dist/core/components/ns-timeline/ns-timeline-icon.element.d.ts

@@ -6,9 +6,6 @@ import type { NsTimelineEventType } from './ns-timeline-event.element.js';
 export declare class NsTimelineIconElement extends UmbLitElement {
     #private;
     look: NsTimelineEventType;
-    /**
-     *
-     */
     constructor();
     render(): import("lit-html").TemplateResult<1>;
     static styles: import("lit").CSSResult[];

package/dist/modules/mailing-list/edit/actions/import/ns-mailing-list-import-modal.element.d.ts

@@ -17,6 +17,7 @@ export declare class NsMailingListImportModalElement extends NsMailingListImport
     errorMessagePerformImport?: string;
     step: 'upload' | 'mappings' | 'processing' | 'importing' | 'done';
     textValue: string;
+    updateExisting: boolean;
     /** Parsed mappings from server */
     mappings?: ImportRecipientsUploadFileAndParseForMappingResponse;
     importResult?: ImportRecipientsResultsResponseFrontendModel;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@newsletterstudio/umbraco",
   "private": false,
-  "version": "14.0.0-rc1",
+  "version": "14.0.4",
   "type": "module",
   "exports": {
     ".": null,

package/readme.md

@@ -1,74 +1,10 @@
-# Newsletter Studio Client
-This is the frontend files for Newsletter Studio, the project uses Vite and Lit to build web components for the Umbraco backoffice.
+# Newsletter Studio / Umbraco
+Use this package to extend [Newsletter Studio](https://www.newsletterstudio.org) for Umbraco. Please refer to our [documentation](https://www.newsletterstudio.org/documentation/) for details on how use the extension points in the package.
 
-## Develop
-Use 
+While not required, we recommend building extensions using the following technologies:
 
-```bash
-npm run watch
-# or
-npm run build
-```
+* Lit
+* TypeScript
+* Vite
 
-## NPM Package
-The NPM package is built using the npm cli, there is a script ready to execute the build.
-
-### Build NPM Package
-
-```bash
-npm run build:npm
-```
-
-This script will run a Typescript-build, clean the output (in the dist-folder), cleanse the package.json file and use `npm pack` to create the package. After this we also need to publish the artifact to npmjs.org.
-
-```bash
-#TODO: How to publish NPM-package to npmjs.org
-```
-
-### Adding new exports / paths
-In `tsconfig.json` there are a number of `paths` configured. These paths can be used internally to make our own code simpler **BUT** this also means that we probably need to export it in the published NPM-package.
-
-When do we need to publish the path?
-
-* IF the path is used in ANY OTHER component, class or type that is published - the new path also needs to be included in the published NPM-package.
-
-To add a new path to the NPM package we need to:
-
-* [ ] Add the path to the `tsconfig.json`
-* [ ] Add the path to the `package.json`s `exports`-section (note that this is a relative path to the dist-folder created during build).
-* [ ] Add the path to `vite.config.ts` to ensure that the outputed js-file always have the same name (no hash).
-* [ ] Add the path as a a important map in `umbraco-package.json` (In `/NewsletterStudio/wwwroot/App_Plugins/newsletterstudio/`), have it point to the file outputted by vite.
-
-### Local build/install of NPM package
-When we want to try out a new version of the NPM-package we can create a new local build.
-
-Run 
-
-```bash
-npm run build:npm
-```
-
-This will output a `.tgz` file, move/copy this file into the project where we want to test it and install using any of the methods below.
-
-
-```bash
-# Install local package
-npm install "D:\Development\Newsletter Studio\Arkiv\Releases\newsletterstudio-umbraco-14.0.0.tgz"
-```
-
-Or in package.json, just add the path to the file and run `npm install`
-
-```json
-{
-   ...
-  "dependencies": {
-    "@newsletterstudio/umbraco": "./../npm-package-src/newsletter-studio-umbraco-ui-0.0.0.tgz",
-  }
-}
-```
-
-## Debugging
-We have several debugging concepts in the package:
-* `<umb-debug visible></umb-debug>` to show Umbraco contexts
-* `<ns-json-debug .data=${}>` to render a object as json inside a pre-element.
-* `<ns-validation-errors-debug></ns-validation-errors-debug>` to show validation errors from the closest context.
+The [NewsletterStudioContrib](https://github.com/enkelmedia/NewsletterStudioContrib)-project on Github provides several examples and can be used as a starting point for the build setup.