It includes these default configurations:

{* ../../fastapi/openapi/docs.py ln[9:24] hl[18:24] *}

You can override any of them by setting a different value in the argument `swagger_ui_parameters`.

For example, to disable `deepLinking` you could pass these settings to `swagger_ui_parameters`:

{* ../../docs_src/configure_swagger_ui/tutorial003_py310.py hl[3] *}

# Security - First Steps { #security-first-steps }

Let's imagine that you have your **backend** API in some domain.

And you have a **frontend** in another domain or in a different path of the same domain (or in a mobile application).

And you want to have a way for the frontend to authenticate with the backend, using a **username** and **password**.

We can use **OAuth2** to build that with **FastAPI**.

import com.google.common.collect.Sets;
import java.util.Map;
import java.util.Random;
import junit.framework.TestCase;
import org.jspecify.annotations.NullUnmarked;

/**
 * Tests that the different algorithms benchmarked in {@link QuantilesBenchmark} are actually all
 * returning more-or-less the same answers.
 */
@NullUnmarked
@GwtIncompatible
@J2ktIncompatible

 * It interacts with the OpenSearch client to create, update, and delete analyzer settings, as well as to retrieve
 * analyzer names and mappings.
 *
 * <p>Key functionalities include:</p>
 * <ul>
 *   <li>Initializing analyzer settings and mappings.</li>
 *   <li>Retrieving analyzer names for different fields and languages.</li>

Since before **JSON Schema** supported `examples` OpenAPI had support for a different field also called `examples`.

This **OpenAPI-specific** `examples` goes in another section in the OpenAPI specification. It goes in the **details for each *path operation***, not inside each JSON Schema.

And Swagger UI has supported this particular `examples` field for a while. So, you can use it to **show** different **examples in the docs UI**.

        dictionaryItem.id = Long.MIN_VALUE;
        assertEquals(Long.MIN_VALUE, dictionaryItem.getId());
    }

    @Test
    public void test_multipleInstances() {
        // Test that different instances have independent ID values
        TestDictionaryItem item1 = new TestDictionaryItem();
        TestDictionaryItem item2 = new TestDictionaryItem();

        item1.id = 100L;
        item2.id = 200L;

    Property<String> getSomeProperty()
}
class Example {
    Property<NestedType> getNestedProperty()
}
```

This is unnecessary because users will have trouble creating instances of `NestedType` and merging different instances of `NestedType`. It's also more awkward for users to access the properties in the nested property.

If the nested type is a managed type (Gradle can generate its implementation), you can define a nested property with:
```

            when(parent.getLocator()).thenReturn(locator);
            when(locator.getURL()).thenReturn(new URL("file:/"));
            // Throw CIFSException with different cause
            CIFSException differentException = new CIFSException("different error");
            when(locator.getAddress()).thenThrow(differentException);

            // Act + Assert

    }

    @ParameterizedTest
    @ValueSource(bytes = { FileInformation.FILE_BASIC_INFO, FileInformation.FILE_STANDARD_INFO, FileInformation.FILE_INTERNAL_INFO })
    @DisplayName("Test readDataWireFormat with different information levels")
    void testReadDataWireFormatWithDifferentLevels(byte infoLevel) throws SMBProtocolDecodingException {
        response = new Trans2QueryPathInformationResponse(mockConfig, infoLevel);

// along with this program.  If not, see <http://www.gnu.org/licenses/>.

package cmd

import (
	"fmt"
	"os"
	"path"
	"path/filepath"
	"runtime"
	"sort"
	"testing"
)

// Test to check for different input arguments.
func TestReadDirFail(t *testing.T) {
	// Check non existent directory.
	if _, err := readDir("/tmp/non-existent-directory"); err != errFileNotFound {
		t.Fatalf("expected = %s, got: %s", errFileNotFound, err)