You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Command attempted
I'm using the Scaleway CLI, and I'm wondering why fields name are named and cased differently for a same type (e.g. image, only one tested yet), for example in :
$ scw instance image list -o json
# Structure and fields differs from the following
$ scw instance image get <ID> -o json
Is it made on purpose? Maybe something in the back-end I'm not aware of or for backward compatibility? 🔀
Because when developing solutions based on your tool, it would be easier if every field of a same type (and even all types, when fields are common) are named and case identically.
Expected Behaviour
This is just a proposal, just to get an idea of the actual issue. I'm using snake_case 🐍 , but you can implement whatever suits you best, we'll adapt. Because today, it seems to be a mix between CamelCase 🐫 and snake_case 🐍 , and it's not very convenient
Community Note
Command attempted
I'm using the Scaleway CLI, and I'm wondering why fields name are named and cased differently for a same type (e.g. image, only one tested yet), for example in :
Is it made on purpose? Maybe something in the back-end I'm not aware of or for backward compatibility? 🔀
Because when developing solutions based on your tool, it would be easier if every field of a same type (and even all types, when fields are common) are named and case identically.
Expected Behaviour
This is just a proposal, just to get an idea of the actual issue. I'm using snake_case 🐍 , but you can implement whatever suits you best, we'll adapt. Because today, it seems to be a mix between CamelCase 🐫 and snake_case 🐍 , and it's not very convenient
Actual Behaviour
More info
💻 Using
scw
CLI v2.2.3 and same behaviour on v2.2.4Already discussed briefly on Slack, and here I am (thread)
Anyway, it's a great tool. Cheers! 😉
The text was updated successfully, but these errors were encountered: