Remember how our app/file structure looks like:

<img src="/img/tutorial/bigger-applications/package.drawio.svg">

---

The two dots `..`, like in:

```Python
from ..dependencies import get_token_header
```

mean:

* Starting in the same package that this module (the file `app/routers/items.py`) lives in (the directory `app/routers/`)...

    assert '"syntaxHighlight": false' not in response.text, (
        "not used parameters should not be included"
    )
    assert '"syntaxHighlight": {"theme": "obsidian"}' in response.text, (
        "parameters with middle dots should be included in a JSON compatible way"
    )
    assert '"dom_id": "#swagger-ui"' in response.text, (
        "default configs should be preserved"
    )

	{"aaa", "a", 0},
	{"abc", "xyz", -1},
	{"abc", "xcz", 2},
	{"ab☺c", "x☺yz", 2},
	{"a☺b☻c☹d", "cx", len("a☺b☻")},
	{"a☺b☻c☹d", "uvw☻xyz", len("a☺b")},
	{"aRegExp*", ".(|)*+?^$[]", 7},
	{dots + dots + dots, " ", -1},
	{"012abcba210", "\xffb", 4},
	{"012\x80bcb\x80210", "\xffb", 3},
	{"0123456\xcf\x80abc", "\xcfb\x80", 10},
}

var lastIndexAnyTests = []BinOpTest{
	{"", "", -1},
	{"", "a", -1},

<img src="/img/tutorial/extending-openapi/image03.png">

## Change the Theme { #change-the-theme }

The same way you could set the syntax highlighting theme with the key `"syntaxHighlight.theme"` (notice that it has a dot in the middle):

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

That configuration would change the syntax highlighting color theme:

<img src="/img/tutorial/extending-openapi/image04.png">

                "",
                display = ParameterDisplay.PROMPT,
                allowEmpty = false,
                description =
                    "Which performance test to run. Should be the fully qualified class name dot (unrolled) method name. " +
                        "E.g. org.gradle.performance.regression.java.JavaUpToDatePerformanceTest.up-to-date assemble (parallel true)",
            )
            text(
                "testJavaVersion",

        assertEquals("my-bucket-name", getField(gcsConn, "bucketName"));
        assertEquals("object.txt", getField(gcsConn, "objectName"));
    }

    /**
     * Test URL parsing with dots in bucket name.
     */
    public void test_urlParsing_dotsInBucket() throws Exception {
        URL url = new URL("gcs://my.bucket.name/object.txt");
        Handler handler = new Handler();

        assertEquals("my-bucket-name", getField(storageConn, "bucketName"));
        assertEquals("object.txt", getField(storageConn, "objectName"));
    }

    /**
     * Test URL parsing with dots in bucket name.
     */
    public void test_urlParsing_dotsInBucket() throws Exception {
        URL url = new URL("storage://my.bucket.name/object.txt");
        Handler handler = new Handler();

     * This helps ImageMagick correctly identify file formats.
     * @param mimeType The MIME type of the content.
     * @return The file extension including the dot (e.g., ".gif"), or empty string if unknown.
     */
    protected String getExtensionFromMimeType(final String mimeType) {
        if (mimeType == null) {
            return "";
        }

This practice is common enough that it has a name, these environment variables are commonly placed in a file `.env`, and the file is called a "dotenv".

/// tip

A file starting with a dot (`.`) is a hidden file in Unix-like systems, like Linux and macOS.

But a dotenv file doesn't really have to have that exact filename.

///

Was it `upper`? Was it `uppercase`? `first_uppercase`? `capitalize`?

Then, you try with the old programmer's friend, editor autocompletion.

You type the first parameter of the function, `first_name`, then a dot (`.`) and then hit `Ctrl+Space` to trigger the completion.

But, sadly, you get nothing useful:

<img src="/img/python-types/image01.png">

### Add types { #add-types }