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

Hard cache removal - first JSON serialization has an unusual result #682

Closed
Destroy666x opened this issue Aug 30, 2018 · 1 comment
Closed

Comments

@Destroy666x
Copy link

Destroy666x commented Aug 30, 2018

Latest stable JMS Serializer Bundle and JMS Serializer.

Steps to reproduce:

  1. rm -rf var/cache/*
  2. Attempt to JSON serialize any object with exposed fields defined in .yml configuration with jms_serializer service.
  3. The resulting string will look like s:123:"PROPER_JSON_STRING_HERE"; where 123 is the length of the JSON string
  4. Attempt to serialize again - the result will be normal.

I'm sure it's a problem of dependencies, but reporting it here just in case. Is it a bug or is there something I'm doing wrong?

@Destroy666x
Copy link
Author

Never mind, I did more testing and it seems to be related to Redis rather than this library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant