Describe the bug
For some reason I allowed attribute values to have spaces, but forgot to limit the attribute name to a single word. This mostly effects the CSV import/export and nothing else. But to remain consistent I think I should limit users from creating attributes with spaces in them, or at least replace the spaces with underscores or something else.
To Reproduce
Steps to reproduce the behavior:
- Create an attribute with a space in the name
- Set it on a track in the dataset
- download the CSV of the dataset
- re-upload as a new dataset the same source images/video and the CSV that was downloaded
- Notice that the attributes don't work properly or have the proper name/value
Expected behavior
track attributes should be portable across JSON track formats and CSV formats to do this limiting the attribute name to a single word should work.
Describe the bug
For some reason I allowed attribute values to have spaces, but forgot to limit the attribute name to a single word. This mostly effects the CSV import/export and nothing else. But to remain consistent I think I should limit users from creating attributes with spaces in them, or at least replace the spaces with underscores or something else.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
track attributes should be portable across JSON track formats and CSV formats to do this limiting the attribute name to a single word should work.