-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[AppConfig] Default to false if null returned when deserilizing ENABLED in feature flag setting #34091
Conversation
API change check API changes are not detected in this pull request. |
The issue seems to be if a field is missing in the current implementation, you get off step, and are one ahead so nothing is equal. You should only call next if the value is checked. The Spring integration test seems to not have a display name, so |
/azp run java - spring - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
This should fix the pipeline for #34022 |
} | ||
// display name | ||
token = parser.nextToken(); | ||
if (token == JsonToken.FIELD_NAME && DISPLAY_NAME.equals(parser.getCurrentName())) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This field is optional. The value of token here is enabled
. This resulted line 202 skipping the enabled
and getting the VALUE_TRUE
/VALUE_FALSE
, so it is never set.
Glad to see that java - spring - tests passed. The |
/check-enforcer override |
Description
When the ENABLED is null, use the default value false.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines