Skip to content
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

JSON normalizers returns object instead of associative arrays #4

Open
jkowalleck opened this issue Oct 7, 2021 · 1 comment · May be fixed by #150
Open

JSON normalizers returns object instead of associative arrays #4

jkowalleck opened this issue Oct 7, 2021 · 1 comment · May be fixed by #150
Labels
breaking change QA Quality Assurance

Comments

@jkowalleck
Copy link
Member

jkowalleck commented Oct 7, 2021

Json normalizers returns object of stdClass instead of associative arrays

  • therefore revisit the serializes in general and simplify them !

benefit:

  • distinguish key-value stores from lists: lists/sets are arrays, key/value-stores are objects
  • this will help typing a lot !
@jkowalleck jkowalleck added this to the v2 milestone Oct 7, 2021
@jkowalleck jkowalleck added the QA Quality Assurance label Sep 27, 2022
jkowalleck added a commit that referenced this issue Sep 27, 2022
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
@jkowalleck jkowalleck linked a pull request Sep 27, 2022 that will close this issue
jkowalleck added a commit that referenced this issue Sep 28, 2022
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
jkowalleck added a commit that referenced this issue Sep 28, 2022
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
jkowalleck added a commit that referenced this issue Sep 28, 2022
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
@jkowalleck jkowalleck changed the title JSON normalizers returns object of stdClass instead of associative arrays JSON normalizers returns object instead of associative arrays Sep 29, 2022
jkowalleck added a commit that referenced this issue Sep 30, 2022
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
@jkowalleck
Copy link
Member Author

gave it a try, did not like the outcome and the effort.
maybe this will be a feature for a later version.

@jkowalleck jkowalleck removed this from the v2 milestone Oct 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change QA Quality Assurance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant