// Create a mock without calling the constructor
        DcerpcPipeHandle handle = mock(DcerpcPipeHandle.class);

        // Inject the binding using reflection
        Field bindingField = DcerpcHandle.class.getDeclaredField("binding");
        bindingField.setAccessible(true);
        bindingField.set(handle, mockDcerpcBinding);

        // Inject the CIFSContext using reflection

### Container Images

All container images are available as manifest lists and support the described
architectures. It is also possible to pull a specific architecture directly by
adding the "-$ARCH" suffix  to the container image name.

name | architectures
---- | -------------

### Positive Consequences

* **Improved consistency**: The codebase has a uniform language standard
* **Easier onboarding**: New contributors have clear guidance on which spelling to use
* **Better searchability**: Finding code and documentation becomes more predictable
* **Reduced review friction**: Less time spent on spelling corrections during PR reviews
* **Professional appearance**: Consistent APIs and documentation appear more polished

        # Supported options are ['csharp', 'cpp', 'go', 'java', 'javascript', 'python']
        language: ['java', 'javascript']
        # Learn more...
        # https://docs.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#overriding-automatic-language-detection

    steps:
    - name: Checkout repository
      uses: actions/checkout@v6

{* ../../docs_src/extending_openapi/tutorial001_py310.py hl[2,15:21] *}

### Modify the OpenAPI schema { #modify-the-openapi-schema }

Now you can add the ReDoc extension, adding a custom `x-logo` to the `info` "object" in the OpenAPI schema:

{* ../../docs_src/extending_openapi/tutorial001_py310.py hl[22:24] *}

### Cache the OpenAPI schema { #cache-the-openapi-schema }

        // ensure that bouncycastle is on classpath for the all of test types, must happen in evaluateAfter since the rest tests explicitly
        // set the class path to help maintain pure black box testing, and here we are adding to that classpath
        tasks.withType(Test).configureEach { Test test ->
          test.setClasspath(test.getClasspath().plus(extraFipsJars))
        }
      }

    }

    @Test
    public void test_addCondition() {
        // Initialize without container
        emptyGenerator = new EmptyGenerator();

        // Test adding conditions - this should work without container
        emptyGenerator.addCondition("field1", "pattern1");
        emptyGenerator.addCondition("field1", "pattern2");
        emptyGenerator.addCondition("field2", "pattern.*");

     *   <li>Using the model locator to find an existing POM at the resolved location</li>
     * </ul>
     *
     * @param modelLocator the locator to use for finding the related POM file
     * @param relative the relative path to resolve
     * @return a new ModelSource for the resolved POM, or null if:
     *         <ul>
     *           <li>This is not a build source</li>

Vous avez également vu comment gérer [CORS avec le `CORSMiddleware`](../tutorial/cors.md).

Dans cette section, nous allons voir comment utiliser d'autres middlewares.

## Ajouter des middlewares ASGI { #adding-asgi-middlewares }

For the following technical terms, use these specific translations to ensure consistency and clarity across the documentation:

* production (meaning production software or environment): продакшн (do not change the ending, for example, translate `in production` as `в продакшн` (not `в продакшене`))
* completion (meaning code auto-completion): автозавершение
* editor (meaning component of IDE): редактор кода