Você pode adicionar múltiplos parâmetros de corpo para sua *função de operação de rota*, mesmo que a requisição possa ter somente um único corpo.

E o **FastAPI** vai manipulá-los, mandar para você os dados corretos na sua função, e validar e documentar o schema correto na *operação de rota*.

Você também pode declarar valores singulares para serem recebidos como parte do corpo.

# Currently TF2.2.0-rc3 all but the first fake_quant in 
# sequence are dropped.  A correct transalation would retain the second as a requantization
# op.

# CORRECT1:name: "Identity"
# CORRECT1-NEXT: quantization:
# CORRECT1-NEXT: scale: [ 0.007813 ],

			},
		},
		5: {
			desc:       "Correct sha256, nested",
			src:        mustReader(t, bytes.NewReader([]byte("abcd")), 4, "", "", 4),
			size:       4,
			actualSize: 4,
			sha256hex:  "88d4266fd4e6338d13b845fcf289579d209c897823b9217da3e161936f031589",
		},
		{
			desc:       "Correct sha256, nested, truncated",

			pools:          pools,
			name:           "Correct",
			expectedErr:    false,
			expectedUpdate: false,
		},
		{
			meta:           meta,
			pools:          newPools,
			name:           "Correct-Update",
			expectedErr:    false,
			expectedUpdate: true,
		},
		{
			meta:           meta,
			pools:          reducedPools,
			name:           "Correct-Update",
			expectedErr:    false,

	listTypeResourceSchema = `
type: object
properties:
  correct-map:
    type: array
    x-kubernetes-list-type: map
    x-kubernetes-list-map-keys: ["a", "b"]
    items:
      type: object
      required: ["a", "b"]
      properties:
        a:
          type: integer
        b:
          type: integer
  correct-set:
    type: array
    x-kubernetes-list-type: set
    items:

        'paddings': paddings,
        'mode': mode,
    }
    # Make sure the composition python function is correct
    self._assertOpAndComposite([input_], tf.raw_ops.MirrorPad,
                               ops_defs._composite_mirror_pad, kwargs_, kwargs)
    # Make sure the translation and decomposition is correct
    self._assertOpAndComposite([input_],
                               tf.function(gen_pad_ops.new_mirror_pad),

                @TaskAction
                def verify() {
                    assert incomingFiles*.name == ["correct"]
                }
            }
        """
    }

    def "resolve the correct files through artifactView"() {
        expect:
        succeeds ':verifyFiles'
    }

		// interfaces and implementations are mutually exclusive,
		// devirtualization can still select the correct callee for
		// each.
		//
		// If they were not mutually exclusive (for example, two Add
		// calls), then we could not definitively select the correct
		// callee.
		val += m.Multiply(42, selectA(i).Add(one(i), 2))
	}
	return val
}

type AddFunc func(int, int) int

The end result is that if this `istio-iptables` wrapper is used, the correct `iptables` binary should be selected dynamically, regardless of whether the context is a pod, the host, a container, or the host filesystem, or what "default" binary is configured in either the container or the host.

import org.gradle.util.internal.ClosureBackedAction
import org.gradle.util.internal.ConfigureUtil
import spock.lang.Specification

class ScriptSourceAwareImplementationResolverTest extends Specification {

    def "correct implementation for #type coerced to Action is tracked"() {
        expect:
        ScriptSourceAwareImplementationResolver.unwrapBean(implementation as Action) == implementation

        where: