It should provide a way to get a HateoasBuilder instance from the container

[docteurklein]

[willdurand]

Yep. We need to mimic what the JMSSerializerBundle provides :)

[willdurand]

@docteurklein contributions are welcomed :) also, give me the name of your book :p

[docteurklein]

sure :) I'll do as soon as possible.

[docteurklein]

the book is https://github.com/RESTful-Web-APIs It has a github! isn't that cool ? :)

[willdurand]

added to my wish list, we never know :D

[lyrixx]

Ah ok, The bundle does provide an instance of the Hateoas serializer ? So, what does it do? I don't understand. I think it lakes of documentation.

[willdurand]

Well, the bundle does not do anything. It wires Hateoas stuff to the Serializer.

You have to use the serializer service from JMSSerializerBundle, nothing else.

[lyrixx]

ahhh, ok. I did not know that. Thanks.

[lyrixx]

May be this should be added in the doc, because it is not so obvious

[willdurand]

However, this should be documented.

[willdurand]

Yes, sure. Actually, this bundle needs some love.

[adrienbrault]

So, multiple issues:

• No bundle configuration to use another XML Serializer
• No bundle configuration to use another JSON Serializer
• No bundle configuration to configure context variables
• No extension point (tag) configure a service as a context variable
• No extension point (tag) to register an expression function
• No extension point (tag) to register a relation provider resolver

Another issue is that is it not currently possible to use multiple XML Serializers or JSON Serializer with the same compiled container. We could fix that by naming the serializers, and configuring the XML/JSON serializer to use using a subclass of the SerializationContext. This one is mostly about a library refactoring. We would also then use tags to register XML/JSON serializers.

Let me know if I have missed anything. I will create issues for each of those.