Flattens a multi-level array of data and generates a single-level array
+compatible with formdata - a single-level array where the keys use bracket
+notation to signify nested data.
Take value and turn it into an array suitable for inclusion in
+the http body (form parameter). If it's a string, pass through unchanged
+If it's a datetime object, format it in ISO8601
formdata must be limited to scalars or arrays of scalar values,
+or a resource for a file upload. Here we iterate through all available
+data and identify how to handle each scenario
We are able to handle nested ModelInterface. We do not simply call
+json_decode(json_encode()) because any given model may have binary data
+or other data that cannot be serialized to a JSON string
Flattens a multi-level array of data and generates a single-level array
+compatible with formdata - a single-level array where the keys use bracket
+notation to signify nested data.
Take value and turn it into an array suitable for inclusion in
+the http body (form parameter). If it's a string, pass through unchanged
+If it's a datetime object, format it in ISO8601
formdata must be limited to scalars or arrays of scalar values,
+or a resource for a file upload. Here we iterate through all available
+data and identify how to handle each scenario
We are able to handle nested ModelInterface. We do not simply call
+json_decode(json_encode()) because any given model may have binary data
+or other data that cannot be serialized to a JSON string
Flattens a multi-level array of data and generates a single-level array
+compatible with formdata - a single-level array where the keys use bracket
+notation to signify nested data.
Take value and turn it into an array suitable for inclusion in
+the http body (form parameter). If it's a string, pass through unchanged
+If it's a datetime object, format it in ISO8601
formdata must be limited to scalars or arrays of scalar values,
+or a resource for a file upload. Here we iterate through all available
+data and identify how to handle each scenario
We are able to handle nested ModelInterface. We do not simply call
+json_decode(json_encode()) because any given model may have binary data
+or other data that cannot be serialized to a JSON string
Flattens a multi-level array of data and generates a single-level array
+compatible with formdata - a single-level array where the keys use bracket
+notation to signify nested data.
Take value and turn it into an array suitable for inclusion in
+the http body (form parameter). If it's a string, pass through unchanged
+If it's a datetime object, format it in ISO8601
formdata must be limited to scalars or arrays of scalar values,
+or a resource for a file upload. Here we iterate through all available
+data and identify how to handle each scenario
We are able to handle nested ModelInterface. We do not simply call
+json_decode(json_encode()) because any given model may have binary data
+or other data that cannot be serialized to a JSON string
Flattens a multi-level array of data and generates a single-level array
+compatible with formdata - a single-level array where the keys use bracket
+notation to signify nested data.
Take value and turn it into an array suitable for inclusion in
+the http body (form parameter). If it's a string, pass through unchanged
+If it's a datetime object, format it in ISO8601
formdata must be limited to scalars or arrays of scalar values,
+or a resource for a file upload. Here we iterate through all available
+data and identify how to handle each scenario
We are able to handle nested ModelInterface. We do not simply call
+json_decode(json_encode()) because any given model may have binary data
+or other data that cannot be serialized to a JSON string
Flattens a multi-level array of data and generates a single-level array
+compatible with formdata - a single-level array where the keys use bracket
+notation to signify nested data.
Take value and turn it into an array suitable for inclusion in
+the http body (form parameter). If it's a string, pass through unchanged
+If it's a datetime object, format it in ISO8601
formdata must be limited to scalars or arrays of scalar values,
+or a resource for a file upload. Here we iterate through all available
+data and identify how to handle each scenario
We are able to handle nested ModelInterface. We do not simply call
+json_decode(json_encode()) because any given model may have binary data
+or other data that cannot be serialized to a JSON string
Flattens a multi-level array of data and generates a single-level array
+compatible with formdata - a single-level array where the keys use bracket
+notation to signify nested data.
Take value and turn it into an array suitable for inclusion in
+the http body (form parameter). If it's a string, pass through unchanged
+If it's a datetime object, format it in ISO8601
formdata must be limited to scalars or arrays of scalar values,
+or a resource for a file upload. Here we iterate through all available
+data and identify how to handle each scenario
We are able to handle nested ModelInterface. We do not simply call
+json_decode(json_encode()) because any given model may have binary data
+or other data that cannot be serialized to a JSON string
Flattens a multi-level array of data and generates a single-level array
+compatible with formdata - a single-level array where the keys use bracket
+notation to signify nested data.
Take value and turn it into an array suitable for inclusion in
+the http body (form parameter). If it's a string, pass through unchanged
+If it's a datetime object, format it in ISO8601
formdata must be limited to scalars or arrays of scalar values,
+or a resource for a file upload. Here we iterate through all available
+data and identify how to handle each scenario
We are able to handle nested ModelInterface. We do not simply call
+json_decode(json_encode()) because any given model may have binary data
+or other data that cannot be serialized to a JSON string