Closed fellipetav closed 10 months ago
Hey @harinij, mind if I take this up?
The field name conversion takes place here (i.e. from myURL
to myUrl
, for example).
However, I don't think removing the conversion (so the field key stays the same as the actual column name) is the right solution. The fact that the the field key is customizable by the user (when initially creating the column manually), means that no standard conversion (camelCase
, or otherwise) -- or even no conversion at all -- is guaranteed to work in every case.
camelCase
form. Then we can always obtain the field key using the same conversion.The latter option is obviously a lot more flexible and gives the users greater control. Please do let me know if I missed something.
@fellipetav this is fixed in our recent release by @nithinrdy 🎉
- Another option is to allow the user to manually enter/change the field keys at the time of importing a CSV, as part of the import CSV wizard.
@nithinrdy , this option is great!
Describe the bug Consider you have some data to be imported using a CSV file, and you have column names such as "myURL". After importing, Rowy is creating the respective column name as "myURL" but the key is created as "myUrl". As a result, the field in Firestore is consequently wrong.
To Reproduce Steps to reproduce the behavior:
key
string exactly as it is at the name, i.e., "myURL" and "mySecondUrl" (note the last "r" and "l" are lower case).Expected behavior It was expected to Rowy keep the key for the column "myURL" equal to "myURL" instead of "myUrl".
Screenshots Not applicable.
Rowy Run version Rowy v3.0.0
Desktop (please complete the following information):
Smartphone (please complete the following information): Not applicable.
Additional context Not applicable.