import org.codelibs.fess.app.web.admin.crawlinginfo.EditForm;

/**
 * Request body class for crawling info edit operations in the admin REST API.
 * This class extends EditForm to inherit the necessary form validation and binding capabilities
 * for crawling information management operations.
 */
public class EditBody extends EditForm {

    /**
     * Default constructor.
     */
    public EditBody() {
        super();
    }

/**
 * Request body class for protected words dictionary edit operations in the admin REST API.
 * This class extends EditForm to inherit the necessary form validation and binding capabilities
 * for protected words dictionary management operations.
 */
public class EditBody extends EditForm {

    /**
     * Default constructor.
     */
    public EditBody() {
        super();

/**
 * Request body class for stemmer override dictionary edit operations in the admin REST API.
 * This class extends EditForm to inherit the necessary form validation and binding capabilities
 * for stemmer override dictionary management operations.
 */
public class EditBody extends EditForm {

    /**
     * Default constructor.
     */
    public EditBody() {
        super();

In that case, they will be applied to all the *path operations* in the application:

{* ../../docs_src/dependencies/tutorial012_an_py39.py hl[16] *}


And all the ideas in the section about [adding `dependencies` to the *path operation decorators*](dependencies-in-path-operation-decorators.md){.internal-link target=_blank} still apply, but in this case, to all of the *path operations* in the app.

This is in contrast to the **development** stages, where you are constantly changing the code, breaking it and fixing it, stopping and restarting the development server, etc.

## Deployment Strategies { #deployment-strategies }

There are several ways to do it depending on your specific use case and the tools that you use.

https://github.com/google/guava/wiki/HowToContribute#code-contributions
and
https://github.com/google/guava/blob/master/CONTRIBUTING.md
before sending a pull request.

We generally welcome PRs for fixing trivial bugs or typos, but please refrain
from sending a PR with significant changes unless explicitly requested.

@SuppressWarnings("JUnit4ClassUsedInJUnit3")
public abstract class AbstractMultisetSetCountTester<E> extends AbstractMultisetTester<E> {
  /*
   * TODO: consider adding MultisetFeatures.SUPPORTS_SET_COUNT. Currently we
   * assume that using setCount() to increase the count is permitted iff add()
   * is permitted and similarly for decrease/remove(). We assume that a

And then you also read how to handle [CORS with the `CORSMiddleware`](../tutorial/cors.md){.internal-link target=_blank}.

In this section we'll see how to use other middlewares.

## Adding ASGI middlewares { #adding-asgi-middlewares }

As **FastAPI** is based on Starlette and implements the <abbr title="Asynchronous Server Gateway Interface">ASGI</abbr> specification, you can use any ASGI middleware.

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.cli.Options;

/**
 * Defines the options specific to the Maven Shell tool.
 * This interface extends the general {@link Options} interface, adding shell-specific configuration options.
 *
 * @since 4.0.0
 */
@Experimental

    }

    @Test
    void testToStringWithoutOptionsAndEndpoint() {
        String expected = PROTO + ":" + SERVER + "[null]";
        assertEquals(expected, dcerpcBinding.toString(), "toString should correctly represent the binding without options or endpoint.");
    }

    @Test
    void testToStringWithEndpoint() throws DcerpcException {
        String endpoint = "\\pipe\\srvsvc";
        dcerpcBinding.setOption("endpoint", endpoint);