Skip to content
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

feat(saveSynonyms): replaceExistingSynonyms -> clearExistingSynonyms #1226

Merged
merged 1 commit into from
Nov 18, 2020

Conversation

Haroenv
Copy link
Contributor

@Haroenv Haroenv commented Nov 16, 2020

fixes #1224

): Readonly<WaitablePromise<SaveSynonymsResponse>> => {
return saveSynonyms(base)(synonyms, {
...requestOptions,
replaceExistingSynonyms: true,
Copy link
Contributor Author

Choose a reason for hiding this comment

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

if someone called replaceAllSynonyms with replaceExistingSynonyms: false, this would be a breaking change, however it's an excluded parameter, therefore not using typescript and not supported usage (wrong parameters)

@codesandbox-ci
Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 4091d67:

Sandbox Source
javascript-client-app Configuration

@Haroenv Haroenv merged commit 2fcf485 into master Nov 18, 2020
@Haroenv Haroenv deleted the feat/clear-existing-synonyms branch November 18, 2020 15:08
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.

Rename replaceExistingSynonyms to clearExistingSynonyms
3 participants