Skip to content

Requests with content-type application/json do not parse params correctly #1337

@crimson-knight

Description

@crimson-knight

When sending a request with the header content-type: application/json with a body that has any kind of valid nested objects, the body is not parsed entirely.

For example:

a POST with content-type application/json in the header and body of:

{
  "ids": [1,2,3]
}

Would be parsed by Amber as:

params["ids"]  # "[1,2,3]" <- with a value as a type of String
{
 "example_object": {
    "another_object": "test"
  }
}

Would be parsed by Amber as:

params["example_object"] # "{ \"another_object\": \"test\" }" 

The expected result is that for this type of request that the entire request body be accessible as a JSON object.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions