}
    },
    "analyzer": {
      "sv_analyzer": {
        "type": "custom",
        "tokenizer": "standard",
        "filter": ["lowercase", "swedish_stop", "swedish_stemmer"]
      }
    }
  }
}
```

### 2. Add Custom Dictionaries (Optional)

Create custom dictionary files in: `${fess.dictionary.path}/[lang]/`

Available dictionary types:

   *
   * <p>Subclasses can override this method to provide custom equality.
   */
  @Override
  public boolean equals(@Nullable Object obj) {
    return super.equals(obj);
  }

  /**
   * By default delegates to {@link Object#hashCode}. The dynamic proxies' {@code hashCode()} will
   * delegate to this method. Subclasses can override this method to provide custom equality.
   */
  @Override
  public int hashCode() {

## Base64 vs Files { #base64-vs-files }

Consider first if you can use [Request Files](../tutorial/request-files.md) for uploading binary data and [Custom Response - FileResponse](./custom-response.md#fileresponse--fileresponse-) for sending binary data, instead of encoding it in JSON.

JSON can only contain UTF-8 encoded strings, so it can't contain raw bytes.

{* ../../docs_src/stream_data/tutorial001_py310.py ln[44:47] hl[47] *}

## A Custom `PNGStreamingResponse` { #a-custom-pngstreamingresponse }

In the examples above, the data bytes were streamed, but the response didn't have a `Content-Type` header, so the client didn't know what type of data it was receiving.

You can create a custom sub-class of `StreamingResponse` that sets the `Content-Type` header to the type of data you're streaming.

# For most projects, this workflow file will not need changing; you simply need
# to commit it to your repository.
#
# You may wish to alter this file to override the set of languages analyzed,
# or to provide custom queries or build logic.
name: "CodeQL"

on:
  push:
    branches: [master]
  pull_request:
    # The branches below must be a subset of the branches above
    branches: [master]
  schedule:
    - cron: '0 11 * * 4'

jobs:

        assertNotNull(ioException);
        assertTrue(ioException.getCause() instanceof java.io.IOException);

        // Test with custom exception
        Throwable customCause = new FessSystemException("Custom Fess error");
        GsaConfigException customException = new GsaConfigException("GSA custom error", customCause);
        assertNotNull(customException);
        assertTrue(customException.getCause() instanceof FessSystemException);

        // Create a fresh circuit breaker for this test to avoid state pollution
        SmbCircuitBreaker customCb = new SmbCircuitBreaker("custom-test", 3, 2, 1000, 3);

        try {
            // Test that without custom predicate, all failures count
            for (int i = 0; i < 3; i++) {
                final int index = i;
                try {

            }
        }

        return bean;
    }

    /**
     * Parses an XML element looking for the name of a custom implementation.
     *
     * @param parser The XML parser
     * @return Name of the custom implementation; otherwise {@code null}
     */
    private static String parseImplementation(final XmlPullParser parser) {

            plugins {
                id 'elasticsearch.java'
                id 'elasticsearch.publish'
            }
            
            version = "1.0"
            group = 'org.acme'
            description = "custom project description"
        """

        when:
        def result = gradleRunner('assemble').build()

        then:
        result.task(":generatePom").outcome == TaskOutcome.SUCCESS

But now you know how it works, so you can use relative imports in your own apps no matter how complex they are. 🤓

### Add some custom `tags`, `responses`, and `dependencies` { #add-some-custom-tags-responses-and-dependencies }

We are not adding the prefix `/items` nor the `tags=["items"]` to each *path operation* because we added them to the `APIRouter`.