Migrating away from SerializerBundle - a start #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We needed to use the SerializerContext in our project which is why we decided to move to a more recent branch of Serializer. This ServiceProvider doesn't need the SerializerBundle anymore, since it doesn't use any of the events from the bundle.
I haven't done the separator thing thing either, since we don't use that.
So, maybe you could use this as a start to get starting with migrating to Serializer >= 0.11
I also had an issue with the test, but I don't know what is causing it. It seems that the cache dir is created OK, but when serializing, it cannot be accessed anymore: