You can also declare a response using a plain arbitrary `dict`, declaring just the type of the keys and values, without using a Pydantic model.

This is useful if you don't know the valid field/attribute names (that would be needed for a Pydantic model) beforehand.

In this case, you can use `dict`:

{* ../../docs_src/extra_models/tutorial005_py310.py hl[6] *}

## Recap { #recap }

Deployment-related operations.
     * Behavior change:
        * Deployment creates ReplicaSets instead of ReplicationControllers.
        * Scale subresource now has a new <code>targetSelector</code> field in its status. This field supports the new set-based selectors supported
by Deployments, but in a serialized format.
     * Spec change:

        final Map<String, Object> source = new LinkedHashMap<>();
        source.put("field\"name", "value");

        final String json = new JsonIndexExportFormatter().format(source, Collections.emptySet());

        assertTrue(json.contains("\"field\\\"name\": \"value\""));
    }

    @Test
    public void test_jsonFormatter_singleField() {

 */

package com.google.common.hash;

import static java.lang.Math.min;

import com.google.common.annotations.VisibleForTesting;
import com.google.common.primitives.Longs;
import java.lang.reflect.Field;
import java.nio.ByteOrder;
import java.security.AccessController;
import java.security.PrivilegedActionException;
import java.security.PrivilegedExceptionAction;
import java.util.Objects;
import sun.misc.Unsafe;

            }
            return new URL(url);
        }
        return null;
    }

    /**
     * Adds a field extraction rule with pruning option.
     *
     * @param name the field name
     * @param xpath the XPath expression for extraction
     * @param isPruned whether the extracted content should be pruned
     */

    * 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...

```

Notice how no connect events are fired for the second call. It reused the connection from the first request for dramatically better performance.

### EventListener.Factory

            }

            /*
             * no point in calling readParameterWordsWireFormat if there are no more
             * parameter words. besides, win98 doesn't return "OptionalSupport" field
             */

            if (wordCount > 2) {
                readParameterWordsWireFormat(buffer, bufferIndex + 4);

                /* The SMB_COM_NT_CREATE_ANDX response wordCount is wrong. There's an

  private final Object lock = new Object();

  /**
   * The runnable, executor pairs to execute. This acts as a stack threaded through the {@link
   * RunnableExecutorPair#next} field.
   */
  @GuardedBy("lock")
  private @Nullable RunnableExecutorPair runnables;

  @GuardedBy("lock")
  private boolean executed;

  /** Creates a new, empty {@link ExecutionList}. */

                        "uses the unsupported value 'legacy', artifact resolution might fail.");
            }
        }
    }

    // ----------------------------------------------------------------------
    // Field validation
    // ----------------------------------------------------------------------

    /**
     * Asserts:
     * <p/>
     * <ul>
     * <li><code>string.length != null</code>