Closed awwsmm closed 4 years ago
Hi, thanks again for the big support. Just 2 questions, any idea why you changed the indentation and string for the boolean values?
No problem!
The indentation was uneven across the files. Most use 4-space indentation, but some (like by-currency-name
) used 2 (and one file used 3, if I remember correctly). I just changed them to all use 4, which seems to be the most popular among them. Of course, JSON will parse correctly no matter what the indentation level is, but I thought it would be better to just have a consistent indentation scheme across all files.
For the booleans, JavaScript will automatically convert "1"
to true
and ""
to false
, but not all languages will do that. Since this is what was intended anyway, I just changed them myself so that they're more useful to people working in other languages.
Thanks, but i have an issue with the boolean changes, as it will break applications expecting the value to be str, maybe it would have been better to add "0"
for false, but i get your reasoning, the problem is backward compatibility
Thanks, but i have an issue with the boolean changes, as it will break applications expecting the value to be str, maybe it would have been better to add
"0"
for false, but i get your reasoning, the problem is backward compatibility
No worries. Changed them back to strings. Maybe later you can change them to booleans and do a minor version bump.
Anything else you'd like me to change?
Anything else you'd like me to change?
No, thanks this was a big help. thank you!!
...but breaking changes for downstream users. Worth it?