Closed shoshta73 closed 3 weeks ago
So are we dropping remove_duplicate_keys function out becuase json.load already takes in last instace of the key as final value?
Well, it should in any particular case, be able to remove any duplicate key unless something could be set in cases where json and jsonc arrays and objects and other permutations of this, to keep it from removing any necessary duplicate item.
I would avoid duplicating functionality.
Reopening this issue after cheking v8 parser implementation.
So currently as per implentation of AST of javascript, when duplicate keys are encountered in javascript object, no error is reported. Given that JSON is basically subset of javascripts AST used for representing objects without their respective methods atached it handles duplicate keys in same as used javascript parser does.
So my conclusion is that "duplicate key error" message is just a LSP giving a person warning about having duplicate keys.
In my opinion removing remove_duplicate_keys would resolve this issue.
we should look into some sort of pythonesque CI/CD.
I agree with your comments here 100%
we should look into some sort of pythonesque CI/CD.
So more of like buildbot actions rather than GH styled workflows?
I haven't extensively looked at actions/workflows for Python stuff, but yes.
This was recommended:
https://www.youtube.com/watch?v=qznIeQBMTyM https://www.youtube.com/watch?app=desktop&v=WTofttoD2xg
I have notice that when loading json from string
example:
json.load will automatically put data=baz into the dictionary