Actions
Bug #13892
closed
Once added, we don't know if a node property is json or string
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
62
Name check:
Fix check:
Regression:
Description
When we are adding a node property, it's easy to check that the parameter is json or string. There is a validator for that.
But once added, we don't know anymore. And since we are not able to edit a parameter (arg), we can't know ever if Rudder think it's a string or json.
We need to:
- know in the backend what it is,
- display a capsule [json] or [string] depending on that information.
Updated by François ARMAND over 5 years ago
- Related to Bug #12360: It's difficult to know if the node property added is valid json added
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.17 to 4.1.18
Updated by Benoît PECCATTE over 5 years ago
- Effort required set to Small
- Priority changed from 50 to 66
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.18 to 4.1.19
- Priority changed from 66 to 65
Updated by Alexis Mousset about 5 years ago
- Target version changed from 4.1.19 to 4.1.20
Updated by François ARMAND about 5 years ago
- Target version changed from 4.1.20 to 4.1.21
- Priority changed from 65 to 64
Updated by François ARMAND about 5 years ago
- Is duplicate of User story #14593: Add a "Copy to clipboard" button for Node properties and show its type added
Updated by François ARMAND about 5 years ago
- Status changed from New to Rejected
- Priority changed from 64 to 62
I'm closing that one as it was superseeded by #14593
Actions