Javascript SDK all strings defined as arrays

The FIT binary protocol allows for any field to be an array, regardless of what is in the profile. Within the file, the message definitions contain the data type and byte count for a field. By dividing the byte count by the size of the data type the decoder can figure out if a field is an array or not. Strings are handled differently. FIT uses C style strings and the null terminator is used as a delimiter to determine if the field contains an array of strings or not.

In the JavaScript SDK string fields are assumed to be an array and then converted to a single value if the length of the array is one.

https://github.com/garmin/fit-javascript-sdk/blob/main/src/stream.js#L189 

The same thing is true for other data types,

https://github.com/garmin/fit-javascript-sdk/blob/main/src/utils-internal.js#L18  

There are times when it looks like a field is an array of strings when it is not, which is discussed here
https://forums.garmin.com/developer/fit-sdk/f/discussion/312373/how-to-parse-a-message-containing-an-array-of-strings 

The repos in GitHub are where the source code for the SDKs is published, so any PR would be written over the next time code is published. Plus, Profile.js is generated, not hand coded, so any change would need to be made in the code generator.

Profile.js and Profile.xlsx are both generated from the same config files, so in theory we should be able to correctly say if a string field is an array or not and correct what is in Profile.js. 

Understood. Thanks for your answer! And I will not submit a PR. Given the nature of the Profile.js, it's no wonder that it's generated!
Indeed, that would be awsome if the Profile "array" value could reflect the real nature of each field!

Thanks!

Jan