Possible bug for Marshmallow fields

I’ve been having trouble setting up default values for the Integer field. I tried using both load_default and default parameters to no avail. It still resulted in the following error message:

{
  "Code": 422, 
  "errors": {
    "query": {
      "page": [
        "Not a valid integer."
      ]
    }
  }
}

In the Schema, I also have a string field. As I am using webargs, I removed the user parameter from the url, and I did get an error message coming from the string field that was similar to the integer one. I’m not sure whether I did something wrong when assigning default values but if I didn’t, then there might be a potential bug with the source code for marshmallow.

Schema:

class AccountUserManagementWebArgs(Schema):
    """
    account user management schema
    """

    user = fields.String(required=True)
    page = fields.Integer(default=1)
    actions = fields.Nested(_account_user_management_webargs_nested, many=True)

[lafrech]

I won’t dig through the whole code sample but

The main goal is that the default value for a schema item should be returned as None if it isn’t found in the url parameter

  "page": [
    "Not a valid integer."
  ]

Could it be you parser sets None as default for all query args, including pagination query args and then you get None for page, which is invalid?

(You may try to send a request with a value for page and see what happens.)

[lafrech]

Great. Closing this, then.