user, err := schema.Parse(&UserWithPermissionControl{}, &sync.Map{}, schema.NamingStrategy{})
	if err != nil {
		t.Fatalf("Failed to parse user with permission, got error %v", err)
	}

	fields := []*schema.Field{
		{Name: "ID", DBName: "id", BindNames: []string{"ID"}, DataType: schema.Uint, PrimaryKey: true, Size: 64, Creatable: true, Updatable: true, Readable: true, HasDefaultValue: true, AutoIncrement: true},

///

### JSON Schema's `examples` field { #json-schemas-examples-field }

But then JSON Schema added an [`examples`](https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.9.5) field to a new version of the specification.

And then the new OpenAPI 3.1.0 was based on the latest version (JSON Schema 2020-12) that included this new field `examples`.

     * @param fields array of fields to search in
     * @param excludes array of words to exclude from results
     * @return list of popular words matching the criteria
     */
    public List<String> getWordList(final SearchRequestType searchRequestType, final String seed, final String[] tags, final String[] roles,
            final String[] fields, final String[] excludes) {

    }

    /**
     * Adds a field and text pair to the field log for tracking query terms.
     * @param field The field name.
     * @param text The query text for this field.
     */
    public void addFieldLog(final String field, final String text) {
        if (fieldLogMap == null) {
            return;
        }

        List<String> list = fieldLogMap.get(field);
        if (list == null) {

	// ErrModelValueRequired model value required
	ErrModelValueRequired = errors.New("model value required")
	// ErrModelAccessibleFieldsRequired model accessible fields required
	ErrModelAccessibleFieldsRequired = errors.New("model accessible fields required")
	// ErrSubQueryRequired sub query required
	ErrSubQueryRequired = errors.New("sub query required")
	// ErrInvalidData unsupported data

                try {
                    suggester.settings().array().add(SuggestSettings.DefaultKeys.SUPPORTED_FIELDS, field);
                } catch (final SuggestSettingsException e) {
                    logger.warn("Failed to add suggest field: field={}", field, e);
                }
            }));

            for (Field field : clazz.getDeclaredFields()) {
                // Skip static fields and synthetic fields
                if (Modifier.isStatic(field.getModifiers()) || field.isSynthetic()) {
                    continue;
                }

                try {
                    field.setAccessible(true);
                    Object value = field.get(node);

     * Specifies the language preference if redirection fails.
     */
    public String lang;

    /**
     * Additional fields map for error page fallback.
     * Contains extra search parameters as key-value pairs if redirection fails.
     */
    public Map<String, String[]> fields = new HashMap<>();

    fields `username` and `password`.

    All the initialization parameters are extracted from the request.

    The only difference between `OAuth2PasswordRequestFormStrict` and
    `OAuth2PasswordRequestForm` is that `OAuth2PasswordRequestFormStrict` requires the
    client to send the form field `grant_type` with the value `"password"`, which

        try {
            java.lang.reflect.Field ptypeField = jcifs.dcerpc.DcerpcMessage.class.getDeclaredField("ptype");
            ptypeField.setAccessible(true);
            assertEquals(0, ptypeField.get(msrpcSamrOpenAlias), "ptype should be initialized to 0");

            java.lang.reflect.Field flagsField = jcifs.dcerpc.DcerpcMessage.class.getDeclaredField("flags");