-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: slice types should be omitted when empty, else they are 'null' in resulting JSON #14
Labels
type: bug
Something isn't working
Comments
devillecodes
changed the title
Array types should be omitted when empty, else they are 'null' in resulting JSON
Slice types should be omitted when empty, else they are 'null' in resulting JSON
Nov 26, 2020
ianaya89
pushed a commit
that referenced
this issue
Jul 6, 2021
* make AlertSettings pointer types; fixes #13 * add omitempty to optional slices; fixes #14 Co-authored-by: Nacho Anaya <[email protected]>
ianaya89
changed the title
Slice types should be omitted when empty, else they are 'null' in resulting JSON
bug: slice types should be omitted when empty, else they are 'null' in resulting JSON
Jun 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The resulting JSON for the
checkly.Check
struct containsnull
values for slice values that are not provided. Examples of this are:Check.Locations
Check.EnvironmentVariables
Check.Tags
Request.Headers
Request.QueryParameters
Request.Assertions
We should add the
,omitempty
annotation so that these values are not passed asnull
in the JSON.The text was updated successfully, but these errors were encountered: