Actions
Bug #15645
closed
[Workbench2] Property Keys are converted into Camel Case Format in Collection View
Status:
Duplicate
Priority:
Normal
Assigned To:
Category:
-
Target version:
Story points:
-
Description
Observation
When assigning properties keys are converted into camel case format. This means keys like "Study Source" become "studySource" and "Phase" becomes "phase". It seems this issue only applies to the collection view, not the project view
Expected
Properties are stored and displayed as entered and stay like this.
It requires at least two changes to a collection and a page reload between.
- Open a collection view and add any property with a multi word key (e.g. "Study Source")
- Refresh the page. The key will change to "studySource" after a moment
- Open Chrome Devtools and add another property. Check the API PUT request payload, it will contain the property key in camel case.
- Afterwards, the property key is persisted as camel case
Related issues
Updated by Tom Morris over 4 years ago
- Related to Bug #15407: [WB2] Property keys on collections are getting translated from snake_case to camelCase added
Updated by Tom Morris over 4 years ago
- Assigned To set to Lucas Di Pentima
I think that this is a duplicate which is already resolved, but assigning to Lucas to double check when he returns from vacation
Updated by Lucas Di Pentima over 4 years ago
Correct. This is a duplicate of #15407, it should be included on the next release.
Updated by Tom Morris over 4 years ago
- Related to deleted (Bug #15407: [WB2] Property keys on collections are getting translated from snake_case to camelCase)
Updated by Tom Morris over 4 years ago
- Is duplicate of Task #15509: Review 15407-camel-casing-fix added
Updated by Tom Morris over 4 years ago
- Is duplicate of Bug #15407: [WB2] Property keys on collections are getting translated from snake_case to camelCase added
Updated by Tom Morris over 4 years ago
- Is duplicate of deleted (Task #15509: Review 15407-camel-casing-fix)
Actions