Project

General

Profile

Bug #12360

It's difficult to know if the node property added is valid json

Added by François ARMAND 8 months ago. Updated 5 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Priority:
64

Description

When we add a property to a node through the UI, if the property is not valid JSON (because we forgot something for ex), Rudder will happily stringify the value. Which is nice from him, but is a disaster from an usability point of view. We must provide to the user a mean so that he can assess "here Rudder, this is JSON, yell at me if you don't understand".

That could be a little dropdown at the begining of the "value" part where the user would choose between "string" and "json", and Rudder would act accordingly.


Related issues

Related to ncf - User story #12691: Add a JSON validator in JSON fields in the editorNew
Related to Rudder - Bug #13892: Once added, we don't know if a node property is json or stringNew

Associated revisions

Revision aaad2dfb (diff)
Added by Raphaël Gauthier 6 months ago

Fixes #12360: It's difficult to know if the node property added is valid json

History

#1 Updated by François ARMAND 8 months ago

  • Effort required changed from Very Small to Small
  • Priority changed from 79 to 66

Raphael, could you evaluate the difficulty for that? It seems that it's pure JS, with a select box that let users choose between string|json (perhaps like the one that let user choose between normal|js in directive parameters), plus a JS check that the input is JSON on [Add] click when JSON is chosen, plus a "stringify" call on [Add] click when "string" is chosen (to force json to became a string) - and actually, the logic on [add] click is more likelly "try to parse value as JSON. If it succeed and string is selected, stringify. If it fails and json is selected, error message. In other case do nothing".

#2 Updated by Raphael GAUTHIER 8 months ago

I think it is not that hard and can be done in one day. Plus maybe another day to validate the UI and the error message, so 2 days should be enough.

#3 Updated by Raphael GAUTHIER 8 months ago

  • Status changed from New to In progress
  • Assignee set to Raphael GAUTHIER

#4 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 4.1.11 to 4.1.12

#5 Updated by Raphael GAUTHIER 8 months ago

  • Status changed from In progress to New

#6 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 4.1.12 to 4.1.13

#7 Updated by Benoît PECCATTE 7 months ago

  • Target version changed from 4.1.13 to 411
  • Priority changed from 66 to 65

#8 Updated by Benoît PECCATTE 7 months ago

  • Target version changed from 411 to 4.1.13

#9 Updated by François ARMAND 6 months ago

  • Related to User story #12691: Add a JSON validator in JSON fields in the editor added

#12 Updated by Raphael GAUTHIER 6 months ago

  • Status changed from New to Pending technical review
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1967

#13 Updated by Normation Quality Assistant 6 months ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Vincent MEMBRÉ to Raphael GAUTHIER
  • Priority changed from 65 to 64

#14 Updated by Raphael GAUTHIER 6 months ago

  • Status changed from Discussion to Pending technical review
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ

#15 Updated by Normation Quality Assistant 6 months ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Vincent MEMBRÉ to Raphael GAUTHIER

#16 Updated by Raphael GAUTHIER 6 months ago

  • Status changed from Discussion to Pending technical review
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ

#17 Updated by Anonymous 6 months ago

  • Status changed from Pending technical review to Pending release

#18 Updated by Vincent MEMBRÉ 5 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.13, 4.2.7 and 4.3.3 which were released today.

#19 Updated by François ARMAND 21 days ago

  • Related to Bug #13892: Once added, we don't know if a node property is json or string added

Also available in: Atom PDF