Skip to content

fix(API): Create Custom Metadata endpoint fix [TSI-2222]#499

Merged
jablan merged 5 commits intomasterfrom
tsi-2222-custom-metadata-create-fix
Jan 2, 2024
Merged

fix(API): Create Custom Metadata endpoint fix [TSI-2222]#499
jablan merged 5 commits intomasterfrom
tsi-2222-custom-metadata-create-fix

Conversation

@jablan
Copy link
Copy Markdown
Collaborator

@jablan jablan commented Dec 19, 2023

Update Custom Metadata non-GET endpoints so that they comply with our standard way of passing parameters.

@jablan jablan changed the title test(go): Add CM create test [TSI-2222] fix(API): Create Custom Metadata endpoint fix [TSI-2222] Dec 20, 2023
@jablan jablan marked this pull request as ready for review December 20, 2023 15:56
ProjectIds: []string{"project_id", "project_id2"},
}
localVarOptionals := phrase.CustomMetadataPropertyCreateOpts{}
resp, httpRes, err := apiClient.CustomMetadataApi.CustomMetadataPropertyCreate(context.Background(), "account_id", customMetadataPropertiesCreateParameters, &localVarOptionals)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one question passing customMetadataPropertiesCreateParameters here is equivalent to passing these arguments individually

(ctx _context.Context, accountId string, name string, dataType CustomMetadataDataType

in the actual api /clients/go/api_custom_metadata.go?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, these individual arguments are replaced by this PR with CustomMetadataPropertiesCreateParameters struct. technically, it's a breaking change, but I don't think anyone is using this yet.

Comment thread paths/custom_metadata_properties/update.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants