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
As per the documentation (haven't verified yet through the CLI) the response from the lease-status command has an inconsistency in the casing as shown in the example:
As seen the ips object follows a PascalCase notation, different to the snake_cased used across all the other responses. It's important to keep the consistency for systems that integrate with the provider-services. If it makes sense some form of guidelines could be developed for future contributions to make sure a standard is followed that will allow integrations to be developed with less friction points such as these. 😄
Update:
Based on this file there seems to be the "correct" json tags, although it is not reflected in the documentation:
As per the documentation (haven't verified yet through the CLI) the response from the
lease-status
command has an inconsistency in the casing as shown in the example:As seen the
ips
object follows a PascalCase notation, different to the snake_cased used across all the other responses. It's important to keep the consistency for systems that integrate with theprovider-services
. If it makes sense some form of guidelines could be developed for future contributions to make sure a standard is followed that will allow integrations to be developed with less friction points such as these. 😄Update:
Based on this file there seems to be the "correct" json tags, although it is not reflected in the documentation:
I'm not sure whether this is the struct that is serialized by the CLI.
Update 2:
This seems to be the serialized structs but there is the IPs struct missing which confuses me https://github.com/ovrclk/provider-services/blob/main/cluster/types/v1beta2/types.go
The text was updated successfully, but these errors were encountered: