import jakarta.validation.constraints.Size;

/**
 * Form class for editing user groups in the admin interface.
 * This form extends CreateForm to include fields necessary for updating existing group entries,
 * including tracking information for optimistic locking and audit trails.
 * Groups are used to organize users and define access permissions.
 *
 */

import jakarta.validation.constraints.Size;

/**
 * Form class for editing path mapping configurations in the admin interface.
 * This form extends CreateForm to include fields necessary for updating existing path map entries,
 * including tracking information for optimistic locking and audit trails.
 * Path mappings are used to transform document URLs and paths during indexing and display.
 *
 */

import jakarta.validation.constraints.Size;

/**
 * Form class for editing related content configurations in the admin interface.
 * This form extends CreateForm to include fields necessary for updating existing related content entries,
 * including tracking information for optimistic locking and audit trails.
 * Related content configurations define relationships between documents for enhanced search results.

import jakarta.validation.constraints.Size;

/**
 * Form class for editing web authentication configurations in the admin interface.
 * This form extends CreateForm to include fields necessary for updating existing web authentication entries,
 * including tracking information for optimistic locking and audit trails.

	PrimaryKey    *Field
	PrimaryValue  string
	ForeignKey    *Field
	OwnPrimaryKey bool
}

func (schema *Schema) parseRelation(field *Field) *Relationship {
	var (
		err        error
		fieldValue = reflect.New(field.IndirectFieldType).Interface()
		relation   = &Relationship{
			Name:        field.Name,
			Field:       field,
			Schema:      schema,
			foreignKeys: toColumns(field.TagSettings["FOREIGNKEY"]),

OAuth2 specifies that when using the "password flow" (that we are using) the client/user must send a `username` and `password` fields as form data.

And the spec says that the fields have to be named like that. So `user-name` or `email` wouldn't work.

But don't worry, you can show it as you wish to your final users in the frontend.

Você pode ler mais no final desta página.

///

## Argumentos adicionais de `Field` { #field-additional-arguments }

Ao usar `Field()` com modelos Pydantic, você também pode declarar `examples` adicionais:

{* ../../docs_src/schema_extra_example/tutorial002_py310.py hl[2,8:11] *}

Puedes leer más al final de esta página.

///

## Argumentos adicionales en `Field` { #field-additional-arguments }

Cuando usas `Field()` con modelos de Pydantic, también puedes declarar `examples` adicionales:

{* ../../docs_src/schema_extra_example/tutorial002_py310.py hl[2,8:11] *}

    }

    /**
     * The search query used to find the document.
     * Optional field with maximum length of 1000 characters.
     */
    @Size(max = 1000)
    public String q;

    /**
     * The document ID of the document to delete.
     * Required field for identifying the specific document.
     */
    @Required
    public String docId;

    /**
     * The unique identifier of the crawling information entry being edited.
     * This is a required field for identifying which crawling info to update.
     */
    @Required
    @Size(max = 1000)
    public String id;

    /**
     * The session identifier of the crawling session.
     * This is a required field that identifies the specific crawling session.
     * Maximum length is 20 characters.
     */
    @Required