strapi-plugin-hubspot 0.7.0 → 0.9.0

package/CHANGELOG.md

@@ -1,5 +1,43 @@
 # Changelog
 
+## 0.9.0 — 2026-08-29
+
+### Added
+- **Import from HubSpot**: forms built in HubSpot (marketing v3 Forms API,
+  `forms` read scope) can be translated into builder drafts — fields, options,
+  two-per-row layouts and dependent-field conditions carried over, with a
+  **CRM mapping that is valid on arrival** since a HubSpot form field is a CRM
+  property. What the builder can't express (file uploads, hidden fields,
+  content blocks, GDPR consent, exotic operators) is skipped and **reported**
+  after the import instead of silently dropped. Re-importing overwrites the
+  draft; the HubSpot original is never touched.
+- **Submissions browser**: a Submissions page in the admin (button on the
+  forms list + per-form counts in the table) — newest first, filterable by
+  form, sync state at a glance, full answers in a modal, and a per-form
+  **CSV export** whose columns follow the field order of the form (historical
+  keys appended, never dropped).
+- Admin routes: `GET/POST /hubspot/builder/import/hubspot`,
+  `GET /hubspot/builder/submissions`, `GET /hubspot/builder/submissions/export`
+  (all RBAC-gated by `plugin::hubspot.forms`); the forms list now carries a
+  `submissions` count per row.
+
+## 0.8.0 — 2026-08-29
+
+### Improved (builder UX pass, from a live session)
+- **The whole step card now selects the step** — the click target was the tiny
+  "Step N" text, which read as "step titles can't be edited". Inner controls
+  stop propagation, so field selection and the action buttons are unaffected.
+- Field panel gains the imported-but-invisible settings: **icon**, **answer
+  memory (persist)** and **CSS classes**; the step and form panels gain **CSS
+  classes** too.
+- **Form-level `class`** now exists end to end: content-type attribute, save,
+  public API, legacy import (it used to be silently dropped on migration).
+- **Duplicate** action on the forms list — every locale of the draft is
+  copied under a fresh slug.
+- Leaving the editor with unsaved changes now warns before the tab closes.
+- Cosmetics: the actions column no longer shows a raw translation key, and the
+  structure column pluralizes properly.
+
 ## 0.7.0 — 2026-08-29
 
 ### Added

package/README.md

@@ -66,6 +66,16 @@ Every submission is stored in **HubSpot form submissions** (Content Manager),
 synced or not, with the CRM ids when the sync succeeded — the source of truth
 lives in your database, not in HubSpot's availability.
 
+### Browsing submissions
+
+The **Submissions** button on the forms list (also reachable from a form's
+count in the table) opens the submissions browser: every stored answer,
+newest first, filterable by form, with the sync state at a glance and the
+full answer set one click away. **Export CSV** downloads one form's whole
+history — columns follow the form's field order, and keys found only in older
+submissions (a renamed or removed field) are appended rather than dropped.
+Deleting stays in the Content Manager, where the type remains visible.
+
 Typed payloads for your frontend:
 
 ```ts
@@ -99,6 +109,24 @@ never modified, re-importing overwrites the draft only, and unpublishing rolls
 a migrated form back. Migrate form by form; the validation middleware keeps
 protecting the ones that stay.
 
+### Importing forms from HubSpot
+
+Forms built **in HubSpot itself** can be imported too — give the private app
+token the `forms` read scope and the list page offers every regular form of
+the portal. The translation carries over what the builder can express:
+
+- fields, labels, placeholders, help texts, required flags and options —
+  and since a HubSpot form field *is* a CRM property, the imported form
+  arrives with a **mapping that is already valid** for the portal;
+- two-fields-per-row layouts become two half-width fields;
+- dependent fields become `visibleIf` conditions (value lists are expanded
+  into OR'd/AND'd rules).
+
+Everything else — file uploads, hidden fields, content blocks, GDPR consent
+blocks, an operator with no equivalent — is **skipped and reported** after the
+import, so nothing is silently half-migrated. The HubSpot original is never
+modified; re-importing overwrites the draft, never the published version.
+
 ### i18n and publishing
 
 Forms are draft & publish, localized like your content: `name` and `slug` are