Kévin Dunglas

You mean for inner documents? We could even use PropertyInfo to get the type instead of adding a new option.

But there is a limitation with this approach: currently JSON ODM allows to store very variable data (`mixed`). With this approach, it's not possible anymore.

It's not totally doable. One great feature of this tool is that you can store totally dynamic data (`mixed` in PHP). For instance, let's imagine the following object graph: ```...

In that case, what do you think about adding HAL and `VndErrorRepresentation` support to DunglasApiBundle. I've started a POC about that (but not finished it yet) and it shouldn't be...

The work to extract the reusable code from the bundle is already done at code level. I've kept everything in a bundle for now because it's simpler to manage and...

The use case it to automatically get a PHP object graph from a JSON string following a normalized format. For instance JSON API define PUT, POST and PATCH formats: http://jsonapi.org/format/...

Topic about support for JSON Pointer, JSON Patch and JSON API on the Doctrine bug tracker: http://www.doctrine-project.org/jira/browse/DDC-2910

We basically use the official Caddy image. I'm not sure there is something we can do here.

We currently lack a Go library implementing [the URLPattern spec](https://wicg.github.io/urlpattern/). The algorithm to implement is fully described in the spec. Some useful resources to implement this: * [Test data](https://github.com/web-platform-tests/wpt/tree/master/urlpattern/resources )...

Hi @si14, Regarding `X-Forwarded-For`, I think that this should be handled at Caddy's level. It's probably already to do this kind of rewrite (but I'm not sure if it's a...