Project

General

Profile

Actions

Bug #23518

open

Error when creating a technique with illegal character parameter

Added by Nicolas CHARLES about 1 year ago. Updated 20 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Technique editor
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

Nothing prevents in the editor to have invalid data, but at save, I have this nasty error


Files

clipboard-202310021333-jnuvs.png (182 KB) clipboard-202310021333-jnuvs.png Nicolas CHARLES, 2023-10-02 13:33
compilation-output.yml (29.2 KB) compilation-output.yml Nicolas CHARLES, 2023-10-02 13:34

Subtasks 1 (0 open1 closed)

Bug #23555: When migrating json technique to yaml, canonify parameter nameReleasedVincent MEMBRÉActions
Actions #1

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 8.0.0~rc1 to 8.0.0~rc2
Actions #2

Updated by François ARMAND about 1 year ago

  • Subtask #23555 added
Actions #3

Updated by François ARMAND about 1 year ago

So there is two part on that bug:

1/ Mapping editor <-> YAML

The first (this ticket) is that the canonization used to be done by rudder webapp and put in the XML. Now, if we want to have it in the yaml, we really need to expose a new field in the technique editor, variable name, which will be used in place of the automatically canonified field.

The UI will pre-fill the input with something sensible from name field. The variable name field must only accept chars in the [\alpha][\alphanum_]* range (ok for vb variable name, ok for cfengine canonification, ok for most lang function name, etc).

Then the mapping is:
- editor hidden field UUID maps to YAML id (optionnal) maps to xml NAME
- editor name maps to YAML description maps to xml DESCRIPTION
- editor variable name maps to YAML name maps to NOTHING in XML
- editor description maps to YAML documentation maps to XML LONGDESCRIPTION

2/ Migration

See #23555

Actions #4

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 8.0.0~rc2 to 8.0.0
Actions #5

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 8.0.0 to 8.0.1
Actions #6

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 8.0.1 to 8.0.2
Actions #7

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 8.0.2 to 8.0.3
Actions #8

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 8.0.3 to 8.0.4
Actions #9

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 8.0.4 to 8.0.5
Actions #10

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 8.0.5 to 8.0.6
Actions #11

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 8.0.6 to 8.0.7
Actions #12

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 8.0.7 to 8.0.8
Actions #13

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 8.0.8 to 8.0.9
Actions #14

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 8.0.9 to 8.0.10
Actions #15

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 8.0.10 to 1089
Actions #16

Updated by Alexis Mousset 5 months ago

  • Target version changed from 1089 to 8.1.6
Actions #17

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 8.1.6 to 8.1.7
Actions #18

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.7 to 8.1.8
Actions #19

Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 8.1.8 to 8.1.9
Actions #20

Updated by Vincent MEMBRÉ 25 days ago

  • Target version changed from 8.1.9 to 8.1.10
Actions #21

Updated by Vincent MEMBRÉ 20 days ago

  • Target version changed from 8.1.10 to 8.1.11
Actions

Also available in: Atom PDF