nucleus-core-ts 0.9.857 → 0.9.859

package/dist/fe/components/IntegrationsPage/components/MappingAccountFields.js

@@ -40,7 +40,13 @@ export function MappingAccountFields({ value, targetFields, targets, disabled, o
         onChange({
             entity: '',
             idColumn,
-            matchColumn: 'email',
+            // Nothing is chosen until the accounts table is, because until then there
+            // is no list to choose from. It used to default to the literal 'email' —
+            // a column this product cannot promise exists, so an installation whose
+            // accounts are identified by a staff number or a username started with a
+            // rule pointing at a column that was not there, and the run failed at the
+            // first account.
+            matchColumn: '',
             matchFrom: emailish,
             passwordColumn: ''
         });
@@ -70,7 +76,9 @@ export function MappingAccountFields({ value, targetFields, targets, disabled, o
                                 onChange: (event)=>patch({
                                         entity: event.target.value,
                                         passwordColumn: '',
-                                        matchColumn: 'email'
+                                        // Cleared, not guessed: the columns of the table just
+                                        // chosen are what the next field offers.
+                                        matchColumn: ''
                                     }),
                                 value: value.entity,
                                 children: [

package/dist/fe/components/IntegrationsPage/components/fieldMappingOptions.js

@@ -26,6 +26,7 @@ export const TRANSFORMS = [
     'toBoolean',
     'dateOnly',
     'emailSafe',
+    'slug',
     'pathLeaf',
     'toList'
 ];
@@ -39,6 +40,7 @@ export const TRANSFORM_LABEL = {
     toBoolean: 'To boolean',
     dateOnly: 'Date only',
     emailSafe: 'E-mail safe (ascii, lowercase)',
+    slug: 'URL slug (ascii, lowercase, hyphens)',
     pathLeaf: 'Last part of a path (A/B/C → C)',
     toList: 'To a list (for a column that holds many)'
 };

package/dist/fe/components/IntegrationsPage/store/index.js

@@ -136,6 +136,16 @@ export const { useStore: useIntegrationsStore } = createStore(initial, {
             store.mappingsLoading = loading;
         },
     selectMapping: (store)=>(id)=>batch(()=>{
+                /*
+       * Choosing the mapping you are already on changes nothing.
+       *
+       * Everything below discards what belongs to the PREVIOUS mapping — its
+       * plan, its running import, its progress. Selecting the same one again
+       * therefore threw away the tracking of an import that was still going:
+       * clicking its row in the list while it ran, or arriving at the step from
+       * a link that re-selected it, left the progress bar gone and the run
+       * apparently finished. It was still writing.
+       */ if (store.selectedMappingId === id) return;
                 store.selectedMappingId = id;
                 // A plan belongs to the mapping it was computed for. Showing it against a
                 // different one would have an operator approve counts from another import.

package/dist/fe/components/IntegrationsPage/types/records.d.ts

@@ -88,7 +88,7 @@ export type IntegrationEndpoint = {
     } | null;
     enabled?: boolean;
 };
-export type MappingTransformValue = 'none' | 'trim' | 'upper' | 'lower' | 'toString' | 'toNumber' | 'toBoolean' | 'dateOnly' | 'emailSafe' | 'pathLeaf' | 'toList';
+export type MappingTransformValue = 'none' | 'trim' | 'upper' | 'lower' | 'toString' | 'toNumber' | 'toBoolean' | 'dateOnly' | 'emailSafe' | 'slug' | 'pathLeaf' | 'toList';
 export type FieldMappingValue = {
     source: string;
     target: string;