Pick doesn't serialise ids correctly for nested model properties about reactivated

[silviogutierrez]

That's nuts, I can't even imagine why it would happen. You're not going through the Pick layer for the ChildInfo. You're manually instantiating it. So I have no explanation.

Should be pretty easy to reproduce with a test in tests/serialization.py. See if you can take a stab then just run pytest.

[silviogutierrez]

You can also just do the reverse relationship, far easier:

Add related_name="children" to the parent = models.ForeignKey declaration. See https://docs.djangoproject.com/en/5.0/ref/models/fields/#django.db.models.ForeignKey.related_name

Then just pick right at the parent level:

Pick[models. ParentModel, "id", "children.id", "children.description"]

And you only need to load the parent and pass it to the template. Magic!

PS. Technically you don't need a related name, just childmodel_set already exists on the parent model. But I don't like that name as much.

[kyczawon]

Realised that my design was probably flawed here. Instead I opted to use pick on the child and do the query on the view & this bug doesn't happen there:

@template
class View(NamedTuple):
    parent: Pick[models. ParentModel, "id", "children_info"]
    children: List[Pick[models. childModel, "id", "description"]]

And then doing the fetch within the view:

parent = get_object_or_404(
        models.ParentModel, org=request.user.current_org, id=prompt_id
    )
children = get_list_or_404(
        models.ChildModel, parent=parent
    )
return templates.View(
        parent=parent,
        children=children,
    ).render(request)