in.peek = true
		in.Push(NewSlice(in.Base(), in.Line(), []Token{Make(macroName, macro.name)}))
		return
	}
	actuals := in.argsFor(macro)
	var tokens []Token
	for _, tok := range macro.tokens {
		if tok.ScanToken != scanner.Ident {
			tokens = append(tokens, tok)
			continue
		}
		substitution := actuals[tok.text]
		if substitution == nil {
			tokens = append(tokens, tok)
			continue
		}

        List<String> expected1 = new ArrayList<>();
        expected1.add("c");
        expected1.add("b");
        expected1.add("a");
        List<String> actual1 = graph1.visitAll();
        assertEquals(expected1, actual1);

        Graph graph2 = new Graph();
        graph2.addVertex("a");
        graph2.addVertex("b");
        graph2.addVertex("c");
        addEdge(graph2, "b", "a");

The webhooks that you define will end up in the **OpenAPI** schema and the automatic **docs UI**.

/// info

The `app.webhooks` object is actually just an `APIRouter`, the same type you would use when structuring your app with multiple files.

///

protocol**.

It is a common practice to have **one program/HTTP server** running on the server (the machine, host, etc.) and **managing all the HTTPS parts**: receiving the **encrypted HTTPS requests**, sending the **decrypted HTTP requests** to the actual HTTP application running in the same server (the **FastAPI** application, in this case), take the **HTTP response** from the application, **encrypt it** using the appropriate **HTTPS certificate** and sending it back to the client using **HTTPS**....

///

The only new thing is the `callbacks=invoices_callback_router.routes` as an argument to the *path operation decorator*. We'll see what that is next.

## Documenting the callback { #documenting-the-callback }

The actual callback code will depend heavily on your own API app.

And it will probably vary a lot from one app to the next.

It could be just one or two lines of code, like:

```Python

/// tip

The instance of the dependency class `OAuth2PasswordRequestForm` won't have an attribute `scope` with the long string separated by spaces, instead, it will have a `scopes` attribute with the actual list of strings for each scope sent.

We are not using `scopes` in this example, but the functionality is there if you need it.

///

* You can get metadata from the uploaded file.
* It has a <a href="https://docs.python.org/3/glossary.html#term-file-like-object" class="external-link" target="_blank">file-like</a> `async` interface.
* It exposes an actual Python <a href="https://docs.python.org/3/library/tempfile.html#tempfile.SpooledTemporaryFile" class="external-link" target="_blank">`SpooledTemporaryFile`</a> object that you can pass directly to other libraries that expect a file-like object.

/**
 * Extracts the filename from the parameters as the content.
 *
 * <p>This extractor is useful when you want to index only the filename or resource name
 * without processing the actual file content. The input stream is validated but not
 * read - only the filename from the parameters is used as the extracted content.</p>
 *
 * <p>The filename is retrieved from the {@link ExtractData#RESOURCE_NAME_KEY} parameter.

* `name`
* `age`

{* ../../docs_src/sql_databases/tutorial002_an_py310.py ln[7:9] hl[7:9] *}

#### `Hero` - the *table model* { #hero-the-table-model }

Then let's create `Hero`, the actual *table model*, with the **extra fields** that are not always in the other models:

* `id`
* `secret_name`

    private final ProjectBuildingResult actual;

    ProjectBuildingResultWithProblemMessageAssert(ProjectBuildingResult actual) {
        this.actual = actual;
    }

    public static ProjectBuildingResultWithProblemMessageAssert assertThat(ProjectBuildingResult actual) {
        return new ProjectBuildingResultWithProblemMessageAssert(actual);
    }