Open errordeveloper opened 5 years ago
sure!
/assign although need to find bandwidth. i'm yet to check https://github.com/kubernetes-sigs/yaml/issues/15 but i suspect discrepancy between the current backends: yaml2 vs encoding/json.
json-iter does support case sensitive JSON.
/kind feature /priority important-longterm
json-iter does support case sensitive JSON.
You mean it can detect unknown keys in case-sensitive manner?
You mean it can detect unknown keys in case-sensitive manner?
yes. i have a PR in the works to enable json-iter. whether it makes it in is another question as it requires a minor breaking change.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
initial reaction was that there is no good justification for this change: https://github.com/kubernetes-sigs/yaml/pull/19 /lifecycle frozen
Looks like there is desire to switch k/k away from json iter.
https://github.com/kubernetes/kubernetes/pull/105030
It suggests using a fork of stdlib, that supports the missing valudation features.
Kubernetes uses
github.com/json-iterator/go
instead ofencoding/json
, should this library switch also?