<root-XML localName="map" namespaceURI="http://docs.oasis-open.org/namespace"/>
    <glob pattern="*.ditamap"/>
  </mime-type>
  <mime-type type="application/dita+xml;format=topic">
    <sub-class-of type="application/dita+xml"/>
    <_comment>DITA Topic</_comment>
    <root-XML localName="topic"/>
    <root-XML localName="topic" namespaceURI="http://docs.oasis-open.org/namespace"/>

        assertFalse(osddHelper.hasOpenSearchFile());

        try {
            osddHelper.asStream();
            fail();
        } catch (final Exception e) {
            assertEquals("Unsupported Open Search Description Document response.", e.getMessage());
        }
    }

    public void test_init_osddpath() throws IOException {
        ComponentUtil.setFessConfig(new FessConfig.SimpleImpl() {
            @Override

{* ../../docs_src/query_params/tutorial005.py hl[6:7] *}

Here the query parameter `needy` is a required query parameter of type `str`.

If you open in your browser a URL like:

```
http://127.0.0.1:8000/items/foo-item
```

...without adding the required parameter `needy`, you will see an error like:

```JSON
{
  "detail": [
    {

                // It is more critical than other attributes because append mode depends on it.
                // We do only really care if we open for writing and not shared for writing
                // otherwise there are no guarantees anyway, but this stuff is legacy anyways.
                final SmbComSeek seekReq = new SmbComSeek(config, 0);

* **Robust**: Get production-ready code. With automatic interactive documentation.

That's why when talking about version 2.0 it's common to say "Swagger", and for version 3+ "OpenAPI".

/// check | Inspired **FastAPI** to

Adopt and use an open standard for API specifications, instead of a custom schema.

And integrate standards-based user interface tools:

* <a href="https://github.com/swagger-api/swagger-ui" class="external-link" target="_blank">Swagger UI</a>

{* ../../docs_src/custom_response/tutorial007.py hl[2,14] *}

#### Utilizando `StreamingResponse` com objetos semelhantes a arquivos

Se você tiver um objeto semelhante a um arquivo (e.g. o objeto retornado por `open()`), você pode criar uma função geradora para iterar sobre esse objeto.

Dessa forma, você não precisa ler todo o arquivo na memória primeiro, e você pode passar essa função geradora para `StreamingResponse` e retorná-la.

}

type format struct {
	ID string `json:"id"`
	XL xl     `json:"xl"`
}

func getMountMap() (map[string]string, error) {
	result := make(map[string]string)

	mountInfo, err := os.Open("/proc/self/mountinfo")
	if err != nil {
		return nil, err
	}
	defer mountInfo.Close()

	scanner := bufio.NewScanner(mountInfo)
	for scanner.Scan() {
		s := strings.Split(scanner.Text(), " ")

* <a href="https://github.com/fastapi/fastapi/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Aquestion+-label%3Aanswered+" class="external-link" target="_blank">📂 ❔</a>

📚 💼 👆 5️⃣📆 ⏪ 💭 ❔ 📚 ❔. 👶

Up to here, everything would work as normally.

But then, when you open the integrated docs UI (the frontend), it would expect to get the OpenAPI schema at `/openapi.json`, instead of `/api/v1/openapi.json`.