chore: update feature flag documentation #34838
Conversation
I feel like the term `default` on a feature flag might be confusing. Replace with the much more pointed "unconfigured behaves like" naming.
| | ----- | ----- | ----- | | ||
| | 1.58.0 | `false` | `true` | | ||
| | 2.0.0 | `true` | `true` | | ||
| | 2.0.0 | `false` | `true` | |
There was a problem hiding this comment.
Is this updating documentation to reflect the correct value, or is there a behaviour change?
I don't see a behavioural change in the code but just checking anyway.
There was a problem hiding this comment.
Hmm that is weird. I'll double check. Thanks for the catch.
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Comments on closed issues and PRs are hard for our team to see. |
4 participants
I feel like the term
defaulton a feature flag might be confusing.Replace with the much more pointed "unconfigured behaves like" naming.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license