REL: 1.2.3

CSV special case corrections, extra data in notifications, documentation

CHANGELOG.md

@@ -2,6 +2,36 @@ CHANGELOG
 =========
 
 
+1.2.3: CSV special case corrections, extra data in notifications, documentation (2023-10-13)
+--------------------------------------------------------------------------------------------
+
+* Corrections to handling of extra data in mailgen template preview
+* Corrections for special cases in CSV data
+* Extended Documentation
+
+## Backend
+* convert example data to Event to handle extra data in database insert:
+  for the mailgen preview, convert the example data to an IntelMQ event
+  and before submitting it to the database, to a dict with extra as a
+  string.
+  Previously, extra-data provided by the user could not be inserted,
+  raising an error
+
+## Frontend
+* frontend: detect if csv data header can be used as field name and use it:
+  if the csv column name (table header) contains a legitimate IntelMQ
+  field name, use this one and skip the further sanitation steps
+* frontend: handle CSV data with no body, but only with a header:
+  if the CSV data contains just one line and the header option is active,
+  the data is body/content-less
+  handle these special cases by aborting the parse and disabling the
+  spinner
+
+## Documentation
+* docs: document format spec (mailgen) influence
+* docs: change URLs to rendered sphinx docs in README
+
+
 1.2.2: Validate Template Preview Data (2023-09-12)
 --------------------------------------------------
 

client/src/components/WebinputCSV.vue

@@ -827,7 +827,7 @@ export default ({
       errorMessage: null,
       showErrorModal: false,
       mailgenTargetGroups: [],
-      clientVersion: "1.2.2",
+      clientVersion: "1.2.3",
       templateDeletionModal: false,
       templateToDelete: {'index': null, 'template_name': null},
       mailgenTemplate: '',

debian/changelog

@@ -1,3 +1,24 @@
+intelmq-webinput-csv (1.2.3-1) UNRELEASED; urgency=medium
+
+  * backend: convert example data to Event to handle extra data in database insert:
+    for the mailgen preview, convert the example data to an IntelMQ event
+    and before submitting it to the database, to a dict with extra as a
+    string.
+    Previously, extra-data provided by the user could not be inserted,
+    raising an error
+  * docs: document format spec (mailgen) influence
+  * docs: change URLs to rendered sphinx docs in README
+  * frontend: detect if csv data header can be used as field name and use it:
+    if the csv column name (table header) contains a legitimate IntelMQ
+    field name, use this one and skip the further sanitation steps
+  * frontend: handle CSV data with no body, but only with a header:
+    if the CSV data contains just one line and the header option is active,
+    the data is body/content-less
+    handle these special cases by aborting the parse and disabling the
+    spinner
+
+ -- Sebastian Wagner <[email protected]>  Fri, 13 Oct 2023 17:48:08 +0200
+
 intelmq-webinput-csv (1.2.2-1) stable; urgency=medium
 
   * Validate Template Preview Data: The user data, (first line of parsed input data), used for the template content validation and preview, validated (sanitized) by IntelMQ before using it for the template preview, otherwise syntactically incorrect values could lead to PostgreSQL errors. Invalid fields are ignored and replaced by example data.

intelmq_webinput_csv/version.py

@@ -1,4 +1,4 @@
 # SPDX-FileCopyrightText: 2017-2018 nic.at GmbH <[email protected]>, 2022-2023 Bundesamt für Sicherheit in der Informationstechnik
 # SPDX-License-Identifier: AGPL-3.0-or-later
-__version_info__ = (1, 2, 2)
+__version_info__ = (1, 2, 3)
 __version__ = '.'.join(map(str, __version_info__))