Marshmallow Two-way Nesting Schemas Validation about flask_accepts

[froggylab]

In order to help, you can find attached the basic configuration I am using :
case-accepts.tar.gz

thank you,

[v1shwa]

@froggylab Were you able to find a solution/workaround for this?

[froggylab]

@v1shwa The only two possibilities I found out were :

• Transmit only the ID of the item you want to send in order for the frontend to do a second request
• import one of the schema directly in your schema class definition (but it's ugly)

[v1shwa]

Thanks for quick response @froggylab . I don't think asking frontend to make another call is an option. I am planning to look into the source & see if we can tweak something. Hopefully, I will raise a PR for this soon.

[ottj3]

Just ran into this myself, for anyone interested here's my workaround, exploiting the fact that marshmallow calculates these string-name-defined schema lazily and stores the result on the schema attribute of the field:

def unpack_nested(val, api, model_name: str = None, operation: str = "dump"):
    if val.nested == "self":
        return unpack_nested_self(val, api, model_name, operation)

+    if isinstance(val.nested, str):
+        parent = val.parent.parent if is_list_field(val.parent) else val.parent
+        parent_name = get_default_model_name(parent)
+        model_name = val.nested + '-in-' + parent_name
+        nested_schema = val.schema
+    else:
        model_name = get_default_model_name(val.nested)
+        nested_schema = val.nested

    if val.many:
        return fr.List(
            fr.Nested(
-                map_type(val.nested, api, model_name, operation), **_ma_field_to_fr_field(val)
+                map_type(nested_schema, api, model_name, operation), **_ma_field_to_fr_field(val)
        )
    )

    return fr.Nested(
-        map_type(val.nested, api, model_name, operation), **_ma_field_to_fr_field(val)
+        map_type(nested_schema, api, model_name, operation), **_ma_field_to_fr_field(val)
    )

I additionally change the model name to <child>-in-<parent>(-load/dump) to prevent conflicts in case your nested fields use only/include/exclude and thus have different fields in their schema. (for_swagger also has to be modified to deal with this, simply add conditions in here: https://github.com/apryor6/flask_accepts/blob/master/flask_accepts/utils.py#L74)

This method can be monkey-patched in via utils.type_map.update({fr.Nested: unpack_nested}) if you want to define it yourself instead of editing the library. (for_swagger can be likewise monkey-patched by updating Schema/SchemaMeta in type_map)

This probably needs some cleanup before being PR-ready material (not even sure if this is a good approach), but it might be a usable workaround for anyone who needs it in the interim.

Bonus: hacky workaround for pluck fields by replacing the first half of that update_nested with

if isinstance(val.nested, str):
    nested_schema = val.schema
else:
    nested_schema = val.nested()

plucked_field = nested_schema.fields[val.field_name]

(and pass plucked_field into map_type instead of nested_schema)