Remove default FixtureMonkeyOptions #1128
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
requested review from
acktsap,
benelog,
jwChung,
mhyeon-lee and
SooKim1110
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Remove default FixtureMonkeyOptions
(Optional): Description
It may be the breaking change. But it compels me for the following reasons.
FixtureMonkeyOptionsinitializes if added in dependency, it causes the unnecessary costs.fixture-monkey-apimodule.We'll recommend to use
FixtureMonkeyOptions.builder().build()instead.How Has This Been Tested?
Is the Document updated?
Later