Hello,

I just give up a test on your bundle... and i like it...

I've got one question: can you explain a little bit how request are handled? As i see, it's all handled via the restController right? What about order by?

Thanks!

👎

Do you handle @OnetoOne relationships ?
Something like:

{
    "fieldA": "...",
    ...
    "b": {
         "fieldB": "...",
         ...
     }
}

doesn't seem to work for me.

POST method: http://localhost/web/web/app_dev.php/api/a.
Where "b" would be the mappedBy field to A)

For more details, I've writte an issue on stackoverflow.

PS: in your Lemon\RestBundle\Object\Manager.php you always make on persist, I think this is why my thing doesn't work.

First phase would be just to register individual entities from the configuration into the object registry. Second phase would be to investigate adding directories that could be iterated through to add entities for. It also seems reasonable to add a configuration directive to turn off the compiler pass that scans bundles.

Thinking out loud...

Would it be better to refer to these as "Resource" instead of "Object"? Principally this is the communication of a object/model/class/blah as a resource.

By convention should something that utilizes a namespace component start with that component in the class name, ie. Lemon\RestBundle\Object\Manager -> Lemon\RestBundle\Object\ObjectManager This seems to be the current convention with a lot of libraries right now.

Hi,
First your bundle is awesome :).
But I have a question, how I can use JMS Serializer groups ?
I defined some groups like "list" and "details" :

• list is for api/entity
• details for api/entity/{id}

For the list group I don't want all the properties of relation, just the id, i.e for a user entity:

[{
    "id": 1,
    "lastname": "Do",
    "firstname": "John",
    "group": 42
},{
    "id": 2,
    "lastname": "Son",
    "firstname": "Thom",
    "group": 21
}]

And for the details group I want all the properties of relation, i.e for a user entity:

{
    "id": 1,
    "lastname": "Do",
    "firstname": "John",
    "group":  {
        "id": 42,
        "name": "anonymous"
    }
}

I tried to use "lemon_rest.event_subscriber" by creating my subscriber, but I feel I can't access to the serializer
Or may be I can try with the "kernel.response" event but it feel to overkill.

I hope my question is clear. I wait your answer

I'm wondering if from a usability stand point it would make sense to render json when the content type is unspecific or 'html', thus meaning that you could navigate end points in the browser pretty easily.

Hi,
When I try to do a get or a post call I get this error:

"The format "" is not supported for serialization"
I have tried with a simple object with only id and name fields.

I haven't found any related issues/fix

Hi, i´ve just followed the Install instructions and after runing symfony it throw the following exception

ParameterNotFoundException in ParameterBag.php line 106:
You have requested a non-existent parameter "jms_serializer.json_serialization_visitor.options".

When I make a GET request in the browser without specifying the Accept header. The default response format is html. The Handler changes it to json.

The issue is that in the response, the Content-Type stays text/html whereas it should be application/json.

I´ve following issue occuring, whenever i make a PUT request by removing a Many-To-Many Entity the complete stack gets deleted.

Owning Side

<?xml version="1.0" encoding="UTF-8" ?>
<doctrine-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-mapping"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mapping
        http://doctrine-project.org/schemas/orm/doctrine-mapping.xsd">

    <entity name="AppBundle\Entity\User" table="user">
        <id name="id" type="integer">
            <generator strategy="AUTO" />
        </id>
        <field name="name" type="string" length="100" />
        <field name="email" type="string" />

        <many-to-many field="roles" inversed-by="users" target-entity="AppBundle\Entity\Role">           
            <join-table name="users_roles">
                <join-columns>
                    <join-column name="user_id" referenced-column-name="id"/>
                </join-columns>
                <inverse-join-columns>
                    <join-column name="role_id" referenced-column-name="id"/>
                </inverse-join-columns>
            </join-table>
        </many-to-many>

    </entity>
</doctrine-mapping>

Role

<?xml version="1.0" encoding="UTF-8" ?>
<doctrine-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-mapping"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mapping
        http://doctrine-project.org/schemas/orm/doctrine-mapping.xsd">

    <entity name="AppBundle\Entity\Role" table="role">
        <id name="id" type="integer">
            <generator strategy="AUTO" />
        </id>
        <field name="name" type="string" length="100" />
        <many-to-many field="users" target-entity="AppBundle\Entity\User" mapped-by="roles">            </many-to-many>
    </entity>
</doctrine-mapping>

Now the Object before:

{
  'user': 'blablalbla...',
  'roles'; [
 { role: 'blablablal'...}
]
}

I make an PUT request with the follwing:

{
  'user': 'blablalbla...',
  'roles'; []
}

And guess what happens? The not only does the joinTable get empty as it should be, but also the Role Entity gets removed from the Repository.

I am still considering the best way to implement this, but at the moment I am leaning towards using a partial object instead of something like JSON Patch (https://tools.ietf.org/html/rfc6902) due to it's lack of support in the wild currently.

I think this can be easily added by taking advantage of the DoctrineObjectConstructor in JMS Serializer. However, the bundle does not make it easy to create a second instance of the serializer with a different constructor, as I need to keep using the standard object constructor with the other request types. I will probably hack something ugly together as a proof of concept and then clean it up in a way that isn't so distasteful thereafter.

This would be a change to the out of the box configuration of LemonRestBundle. I'm noticing most js libraries seem to expect the flattened response and thus I'm leaning towards making this the default behavior.

I've got one for a one-to-one, but it would be nice to test persisting a collection of referential id's as well.

Ember.Data for example nests responses in a property labeled for the resources, for example:

{
  "post": {
     "id": 1
   }
}

Likewise Restangular and tools like ng-admin wants collections that are not nested, something like:

[{}, {}, {}]

Add an envelope factory with an export method and define two different envelope types, an individual object and a collection of objects, and allow this to alter the structure that gets sent to JMS Serializer for serialization. Default behavior should be what's currently done. This would most likely be manipulated through the semantic config being added in #2

The default number of items per page is currently hardcoded in the DefaultCriteria.
It would be nice if this could be in the bundle configuration.

Example:

lemon_rest:
    defaults:
        limit: 500

Is it compatible with Doctrine MongoDB ODM?

Hi,

I would like to POST an entity with a nested collection in a nested collection.
First collection is saved, but second not.
I wrote a test in pull request.