Project

General

Profile

Actions

Bug #8151

closed

Technique Editor - whitespace as separator in "File ensure keys -> values present" method

Added by David Svejda over 8 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Category:
Generic methods
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Creating/modifying my own Technique.

When I use method "File ensure keys -> values present", I cannot put the whitespace in the "Separator between key and value" field as hinted, because when I just hit the Spacebar, it doesn't accept it. I've tried to use the "\s" there, but it doesn't seem to work as expected.


Related issues 1 (0 open1 closed)

Related to Rudder - User story #8228: Add constraints to ncf parametersReleasedBenoît PECCATTEActions
Actions #1

Updated by Vincent MEMBRÉ over 8 years ago

  • Project changed from Rudder to 41
  • Category deleted (Web - Technique editor)
  • Assignee set to Vincent MEMBRÉ
  • Target version set to 0.x
Actions #2

Updated by Vincent MEMBRÉ over 8 years ago

  • Status changed from New to In progress
Actions #3

Updated by Vincent MEMBRÉ over 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/ncf/pull/338
Actions #4

Updated by François ARMAND over 8 years ago

Some more context on the bug: for now, all input fields in the Technique Editor are trimed, and it's the reason why we are seeing the bug.

We can't simply stop triming all fields, because in lots of case, we DO want timming. We are on it.

Actions #5

Updated by Nicolas CHARLES over 8 years ago

As a workaround, we could define somewhere a variable that contains only space, and use it as a separator.

Actions #6

Updated by Nicolas CHARLES over 8 years ago

  • Status changed from Pending technical review to In progress
  • Assignee changed from François ARMAND to Vincent MEMBRÉ

Correctingicket status: it is not in technical review, as the PR has been closed

Actions #7

Updated by Jonathan CLARKE over 8 years ago

  • Subject changed from Technique Editor - whitespace as separator to Technique Editor - whitespace as separator in "File ensure keys -> values present" method
  • Pull Request deleted (https://github.com/Normation/ncf/pull/338)

We are implementing a "constraints" system in ncf (generic methods, API and Technique editor). Once that's ready (later this week), we'll be able to add a constraint to this generic method and fix this.

Actions #8

Updated by Vincent MEMBRÉ over 8 years ago

Actions #9

Updated by Vincent MEMBRÉ over 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/ncf/pull/387
Actions #10

Updated by Vincent MEMBRÉ over 8 years ago

  • Assignee changed from Benoît PECCATTE to François ARMAND
Actions #11

Updated by Vincent MEMBRÉ over 8 years ago

  • Assignee changed from François ARMAND to Benoît PECCATTE
Actions #12

Updated by Vincent MEMBRÉ over 8 years ago

  • Assignee changed from Benoît PECCATTE to François ARMAND
Actions #13

Updated by Vincent MEMBRÉ over 8 years ago

  • Assignee changed from François ARMAND to Benoît PECCATTE
Actions #14

Updated by Vincent MEMBRÉ over 8 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset commit:e75f1d2a7421a9a92a6339d8576ed40bb3e88dab.

Actions #15

Updated by Vincent MEMBRÉ over 8 years ago

  • Status changed from Pending release to Released
Actions #16

Updated by Alexis Mousset over 2 years ago

  • Target version changed from 0.x to ncf-0.x
  • Priority set to 0
Actions #17

Updated by Alexis Mousset over 2 years ago

  • Project changed from 41 to Rudder
  • Category set to Generic methods
Actions

Also available in: Atom PDF