Fix the issue where the configuration of componentType as NORMAL is not effective. #665
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
shalousun
approved these changes
Nov 23, 2023
shalousun
changed the title
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.
The previous PR #661 had issues when merging commits, so it's being resubmitted.
When using the object obtained from ApiConfig.getInstance(), all its fields are unassigned, resulting in getComponentType() returning null and defaulting to the RANDOM mode. An ApiConfig.setInstance() method has been added to initialize ApiConfig.instance.
之前的 PR #661 在合并 commit 的时候有问题，所以重提一个。
使用 ApiConfig.getInstance() 获取的对象，里面的字段都是未赋值的，导致 getComponentType() 为 null，默认走 RANDOM 模式。
增加 ApiConfig.setInstance() 方法，为 ApiConfig.instance 进行初始化。