Test duplicate key behavior in KeyElement#315
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: inteon The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Signed-off-by: Tim Ramlot <42113979+inteon@users.noreply.github.com>
d03357c to
e39bd44
Compare
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
"Investigate whether the original ReadObjectCB function implicitly prevented or handled duplicate key entries in JSON objects. Based on this, create a specific test case to ensure the new json/v2 implementation behaves identically to json-iterator when encountering duplicate keys." - SMD #292 Action items
Adds test case for duplicate keys in KeyElement