/**
 * The search form for Access Token.
 */
public class SearchForm {

    /**
     * Default constructor for SearchForm.
     */
    public SearchForm() {
    }

    /**
     * The ID field for searching access tokens.
     */
    public String id;

			}
			if !c.header {
				args.FileHeaderInfo = none
			}
			r, _ := NewReader(io.NopCloser(bytes.NewReader(input)), &args)
			fields := 0
			for {
				record, err = r.Read(record)
				if err != nil {
					break
				}
				if fields < 10 {
					opts := sql.WriteCSVOpts{
						FieldDelimiter: ',',
						Quote:          '"',
						QuoteEscape:    '"',
						AlwaysQuote:    false,

Para declarar bodies de formularios, necesitas usar `Form` explícitamente, porque sin él, los parámetros se interpretarían como parámetros de query o como parámetros de body (JSON).

///

## Sobre "Campos de formulario" { #about-form-fields }

La manera en que los formularios HTML (`<form></form>`) envían los datos al servidor normalmente usa una codificación "especial" para esos datos, es diferente de JSON.

	"strings"

	color "github.com/minio/minio/internal/color"
)

// Extra ASN1 OIDs that we may need to handle
var (
	oidEmailAddress = []int{1, 2, 840, 113549, 1, 9, 1}
)

// printName prints the fields of a distinguished name, which include such
// things as its common name and locality.
func printName(names []pkix.AttributeTypeAndValue, buf *strings.Builder) []string {
	values := []string{}
	for _, name := range names {

/**
 * The search form for Mapping.
 */
public class SearchForm {

    /**
     * Default constructor for SearchForm.
     */
    public SearchForm() {
    }

    /**
     * The dictionary ID field for mapping dictionary operations.
     */
    @Required
    public String dictId;

    * API fields previously capable of storing and returning either `[]` and `null` via JSON API requests (for example, the Endpoints `subsets` field) can now store only `null` when created using the protobuf content-type or stored in etcd using protobuf serialization (the default in 1.6+). JSON API clients should tolerate `null` values for such fields, and treat `null` and `[]` as equivalent in meaning unless specifically documented...

@SuppressWarnings("JUnit4ClassUsedInJUnit3")
public class AbstractSetTester<E> extends AbstractCollectionTester<E> {
  /*
   * Previously we had a field named set that was initialized to the value of
   * collection in setUp(), but that caused problems when a tester changed the
   * value of set or collection but not both.
   */
  protected final Set<E> getSet() {

import org.codelibs.fess.app.web.admin.dict.mapping.CreateForm;

/**
 * Request body for creating mapping dictionary via REST API.
 * Extends CreateForm to inherit validation and field definitions.
 */
public class CreateBody extends CreateForm {

    /**
     * Creates a new CreateBody instance.
     */
    public CreateBody() {
    }

 */
package org.codelibs.fess.app.web.api.admin.group;

import org.codelibs.fess.app.web.admin.group.CreateForm;

/**
 * Request body for creating group via REST API.
 * Extends CreateForm to inherit validation and field definitions.
 */
public class CreateBody extends CreateForm {

    /**
     * Creates a new CreateBody instance.
     */
    public CreateBody() {
    }

package org.codelibs.fess.app.web.api.admin.accesstoken;

import org.codelibs.fess.app.web.admin.accesstoken.CreateForm;

/**
 * Request body for creating access token via REST API.
 * Extends CreateForm to inherit validation and field definitions.
 */
public class CreateBody extends CreateForm {

    /**
     * Creates a new CreateBody instance.
     */
    public CreateBody() {
    }