Import `BaseSettings` from Pydantic and create a sub-class, very much like with a Pydantic model.

The same way as with Pydantic models, you declare class attributes with type annotations, and possibly default values.

You can use all the same validation features and tools you use for Pydantic models, like different data types and additional validations with `Field()`.

//// tab | Pydantic v2

      - closed
  workflow_dispatch:
    inputs:
      number:
        description: PR number
        required: true
      debug_enabled:
        description: 'Run the build with tmate debugging enabled (https://github.com/marketplace/actions/debugging-with-tmate)'
        required: false
        default: 'false'

env:
  UV_SYSTEM_PYTHON: 1

jobs:
  job:
    runs-on: ubuntu-latest
    permissions:

     */
    protected final List<String> readings;

    /**
     * The list of fields associated with the elevate word.
     */
    protected final List<String> fields;

    /**
     * The list of tags associated with the elevate word.
     */
    protected final List<String> tags;

    /**
     * The list of roles associated with the elevate word.
     */

        assertFalse(auth.matches(""));
        assertFalse(auth.matches(null));

        // Test with different ports
        auth.setPort(8080);
        assertTrue(auth.matches("ftp://hostname:8080/test/aaa.html"));
        assertFalse(auth.matches("ftp://hostname:21/test/aaa.html"));

        // Test with no port specified in FtpAuthentication
        auth.setPort(0);

* `Path()`
* `Query()`
* `Header()`
* `Cookie()`
* `Body()`
* `Form()`
* `File()`

you can also declare a group of `examples` with additional information that will be added to their **JSON Schemas** inside of **OpenAPI**.

### `Body` with `examples` { #body-with-examples }

Here we pass `examples` containing one example of the data expected in `Body()`:

        return mockContext;
    }

    @Nested
    @DisplayName("Constructor Tests")
    class ConstructorTests {

        @Test
        @DisplayName("Constructor with CIFSContext should create message with default flags")
        void testConstructor_CIFSContext() {
            // Given
            CIFSContext mockContext = createMockContext();

            // When

  /**
   * Creates a new {@code AtomicDouble} with the given initial value.
   *
   * @param initialValue the initial value
   */
  public AtomicDouble(double initialValue) {
    value = doubleToRawLongBits(initialValue);
  }

  /** Creates a new {@code AtomicDouble} with initial value {@code 0.0}. */
  public AtomicDouble() {
    // assert doubleToRawLongBits(0.0) == 0L;
  }

    @Test
    @DisplayName("Test setTid with positive value")
    void testSetTidWithPositiveValue() {
        // Given
        int tid = 12345;
        doNothing().when(request).setTid(tid);

        // When
        request.setTid(tid);

        // Then
        verify(request, times(1)).setTid(tid);
    }

    @Test
    @DisplayName("Test setTid with zero value")
    void testSetTidWithZero() {

It is easy to assume that HTTPS is something that is just "enabled" or not.

But it is way more complex than that.

/// tip

If you are in a hurry or don't care, continue with the next sections for step by step instructions to set everything up with different techniques.

///

name: FastAPI People Contributors

on:
  schedule:
    - cron: "0 3 1 * *"
  workflow_dispatch:
    inputs:
      debug_enabled:
        description: "Run the build with tmate debugging enabled (https://github.com/marketplace/actions/debugging-with-tmate)"
        required: false
        default: "false"

env:
  UV_SYSTEM_PYTHON: 1

jobs:
  job:
    if: github.repository_owner == 'fastapi'
    runs-on: ubuntu-latest