Annotation for field that can't be filtered

[AlessandroMinoccheri]

Q	A
Bug report?	no
Feature request?	yes
QueryBundle version	2.4

---

Create an entity annotation on its fields to declare if that field can't be filtered so if a request try to filter with that field the query bundle remove automatically that filter for example the field password. Now that can be done into the request listener but I think is better to Do it into the entity

[sensorario]

This is not a querybundle issue. I mean that data representation is made by JmsSerializer. Check you jms_serializer configuration. Here an example:

jms_serializer:
    metadata:
        directories:
            FooBar:
                namespace_prefix: "Foo\\BarBundle"
                path: "%kernel.root_dir%/serializer/FooBar"
    default_context:
        serialization:
            serialize_null: true

Inside folder ./app/serializer/FooBar/Model.User.yml you whould have the following file content:

Foo\BarBundle\Model\User:
    exclusion_policy: ALL
    properties:
        id:
            expose: true
        username:
            expose: true
        name:
            expose: true
        email:
            expose: true
        enabled:
            expose: true
        divisions:
            expose: true
        additional_filters:
            expose: true

[AlessandroMinoccheri]

Filter is different than expose, I want to be sure that a field can't be passed to query bundle, for example field mobile phone can't be added into query string with filtering but can be exposed.

[sensorario]

👍 ok now I got it