Project

General

Profile

Bug #8473

Form fields in Directive edit are eating leading spaces.

Added by steev hise about 2 years ago. Updated about 1 month ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
Target version (plugin):
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Pull Request:
Priority:
43

Description

Certain form fields seem to delete leading whitespace.
For instance, in the directive form for the enforce file content technique, if the first line of the content starts with whitespace, after you save the whitespace disappears
Also there in the section header and footer fields.
This is important if you're trying to edit a file with indentation on some lines.


Related issues

Related to Rudder - Bug #3656: can't start motd with empty lineNew

History

#1 Updated by steev hise about 2 years ago

the redmine interface seems to have done even worse. heh.
let me try again.

configSectionFoo

becomes
configSectionFoo

#2 Updated by Nicolas CHARLES about 2 years ago

  • Related to Bug #3656: can't start motd with empty line added

#3 Updated by François ARMAND about 2 years ago

We had a similar report some time ago (ticket linked).

There is something to take into account: in some fields, we really expect as a user that the words will be trimed (ex: for a field waiting for a version in package management, for the name, etc).

It seems that a good behaviour would be to NOT TRIM text area (all example proposed are text area, and other examples we thing about where also only "long input").

So:

- we will try to remove trim in long input field kind (text area)
- and check that nothing break :)

Thanks for the report (and the reminder that this is an important topic)

#4 Updated by steev hise about 2 years ago

François ARMAND wrote:

We had a similar report some time ago (ticket linked).

There is something to take into account: in some fields, we really expect as a user that the words will be trimed (ex: for a field waiting for a version in package management, for the name, etc).

It seems that a good behaviour would be to NOT TRIM text area (all example proposed are text area, and other examples we thing about where also only "long input").

So:

- we will try to remove trim in long input field kind (text area)
- and check that nothing break :)

There are some text (short) input fields that it would make sense not to trim to, like anywhere that matching a line in a file, unless a regex is able to entered. For instance in that same example I give above, the enforce file content, section header/footer fields need to allow leading spaces too, or they need to be able to accept a regex. thanks.

#5 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.2.5 to 3.2.6

#6 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.2.6 to 3.2.7

#7 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.2.7 to 3.2.8

#8 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.2.8 to 3.2.9

#9 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.2.9 to 3.2.10

#10 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.2.10 to 3.2.11

#11 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.2.11 to 339

#12 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 339 to 4.0.4

#13 Updated by Benoît PECCATTE about 1 year ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings

#14 Updated by Benoît PECCATTE about 1 year ago

  • Priority set to 31

#15 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.0.4 to 4.0.5

#16 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.0.5 to 4.0.6
  • Priority changed from 31 to 30

#17 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.0.6 to 4.0.7

#18 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.0.7 to 357

#19 Updated by Benoît PECCATTE 12 months ago

  • Priority changed from 30 to 43

#20 Updated by Alexis MOUSSET 12 months ago

  • Target version changed from 357 to 4.1.6

#21 Updated by Benoît PECCATTE 12 months ago

  • Category changed from Web - UI & UX to Web - Config management

#22 Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 4.1.6 to 4.1.7

#23 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 4.1.7 to 4.1.8

#24 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 4.1.8 to 4.1.9

#25 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 4.1.9 to 4.1.10

#26 Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 4.1.10 to 4.1.11

#27 Updated by Vincent MEMBRÉ 2 months ago

  • Target version changed from 4.1.11 to 4.1.12

#28 Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 4.1.12 to 4.1.13

Also available in: Atom PDF