New Feature - Nested Fields

[stunaz]

Hi, Thank you for the lib.
Would it be possible to add a mechanism for nested fields?
i.e. some how :
Given
GET http://127.0.0.1:8000/things/

[
  {
    "id": 1,
    "key1": "val1",
    "key2": "val2",
    "key3":{
      "id": 2,
      "key1": "valA",
      "key2": "valB",
      "key3": "valC",
    },
  }
]

then we could do :

GET http://127.0.0.1:8000/things/?fields=id,key3__id, key3__key2

[
  {
    "id": 1,
    "key3":{
      "id": 2,
      "key2": "valB"
    },
  }
]

[wimglenn]

That's a good idea. I assume you didn't intend to include "key1": "val1", in the example response here? I'll have a look and see what I can do. Handling exclusion queries will need some design decisions - could you add examples for what you think makes most sense for those?

[stunaz]

@wimglenn yes indeed, meant to exclude "key1": "val1", removed it. exclusions would work the same way:
i.e.: with initial example from my first post

GET http://127.0.0.1:8000/things/?fields!=id,key3__id, key3__key2

[
  {
    "key1": "val1",
    "key2": "val2",
    "key3":{
      "id": 2,
      "key3": "valC",
    },
  }
]

[wimglenn]

Why not like this?

[
  {
    "key1": "val1",
    "key2": "val2",
    "key3":{
      "key1": "valA",
      "key3": "valC",
    },
  }
]

[stunaz]

@wimglenn exactly

[mlissner]

FWIW, the other project claims to have this functionality: https://github.com/dbrgn/drf-dynamic-fields/blob/master/drf_dynamic_fields/__init__.py

[wimglenn]

@mlissner Could you clarify? I don't see that claim anywhere there, nor code to support that feature. And there is no test coverage showing nested filtering working.

[mlissner]

Yeah, I didn't see the code either, but I also didn't understand it all. Here's where they claim it supports nested fields:

https://github.com/dbrgn/drf-dynamic-fields/blob/master/CHANGELOG.md#020---2017-04-07

And this seems to (maybe) be where it was implemented (judging by commit msg):

dbrgn/drf-dynamic-fields#14

Not sure. Maybe I'm misunderstanding something?

[adinvadim]

@wimglenn
Any plans to implement this feature?

[jsmedmar]

Hey this would be so amazing!

[johncpang]

Yeah, I didn't see the code either, but I also didn't understand it all. Here's where they claim it supports nested fields:

https://github.com/dbrgn/drf-dynamic-fields/blob/master/CHANGELOG.md#020---2017-04-07

And this seems to (maybe) be where it was implemented (judging by commit msg):

dbrgn/drf-dynamic-fields#14

Not sure. Maybe I'm misunderstanding something?

From my understanding, they are fixing a mistake that the filter ALSO apply to subserializer. For example,

{
    "id": 1,
    "key1": "val1",
    "key2": {
        "id": 2,
        "key1": "valA"
    }
}

If you supply ?omit=key1, the expect result should be:

{
    "id": 1,
    "key2": {
        "id": 2,
        "key1": "valA"
    }
}

But actual result was:

{
    "id": 1,
    "key2": {
        "id": 2,
    }
}

The OP here, however, want to able to filter the nested serializer, and (I believe) should be explicit. So, ?fields!=key1 will only apply to first level but not sub-levels, and ?fields!=key2__key1 will only apply to second level but not root level.

[johncpang]

There is another project that said to have this functionality: drf_tweaks. Just have a brief look in their source and it's much bigger than djangorestframework-queryfields. Some of us prefer smaller better.

Here is a short summary after I tried both of them.

djangorestframework-queryfields works on first level only.
drf_tweaks works on multiple levels (nested-serializer).

djangorestframework-queryfields allows you to define the list of fields you want.
drf_tweaks allows you to define the list of fields you want.

djangorestframework-queryfields allows you to define the list of fields you don't want (and you get all the remainings). If you want all fields, do nothing.
drf_tweaks can do similar but the other way: first excluding them using 'on_demand_fields', and bring them back using '?include_fields='. If you want all fields, you need to use '?include_fields'.

• use "?include_fields=" when you want those fields back.
• do nothing when you want those fields excluded.

Maybe we can include both mixins on serializer (umm the serializer getting fat). Since both of them are available in mixins, we selectively apply one or both per serializer.

[yezyilomo]

I think django-restql is more advanced and simpler, it works much like GraphQL.

[shafiyal]

@mlissner I have checked 'drf-dynamic-fields' package but still it is also not doing fields filtering on nested fields