Project

General

Profile

Actions
Copy link

Bug #15645

closed

[Workbench2] Property Keys are converted into Camel Case Format in Collection View

Added by Moritz Gilsdorf over 5 years ago. Updated about 5 years ago.

Status:
Duplicate
Priority:
Normal
Assigned To:
Lucas Di Pentima
Category:
-
Target version:
Arvados - 2019-10-23 Sprint
Start date:
Due date:
% Done:

0%

Estimated time:
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.

How to reproduce
It requires at least two changes to a collection and a page reload between.
  1. Open a collection view and add any property with a multi word key (e.g. "Study Source")
  2. Refresh the page. The key will change to "studySource" after a moment
  3. Open Chrome Devtools and add another property. Check the API PUT request payload, it will contain the property key in camel case.
  4. Afterwards, the property key is persisted as camel case

Related issues 1 (0 open — 1 closed)

Is duplicate of Arvados - Bug #15407: [WB2] Property keys on collections are getting translated from snake_case to camelCaseResolvedLucas Di Pentima08/19/2019

Actions
Actions
Copy link

Also available in: Atom PDF