testJvmVersion.toCapitalized() +
        "${vendor.displayName}${os.asName()}${arch.asName()}"

// Generates a Build Scan custom value "PartOf=X,Y,Z"
// where X, Y, Z are all the stages including current stage
// For example, for the stage PullRequestFeedback, the custom value will be "PartOf=PullRequestFeedback,ReadyForNightly,ReadyForRelease"
private fun Stage.getBuildScanCustomValues(): List<String> =
    StageName

        // 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 {

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`.

	return fmt.Sprintf("%s%s", c.prefix, fieldValue), nil
}

func TestSerializer(t *testing.T) {
	schema.RegisterSerializer("custom", NewCustomSerializer("hello"))
	DB.Migrator().DropTable(adaptorSerializerModel(&SerializerStruct{}))
	if err := DB.Migrator().AutoMigrate(adaptorSerializerModel(&SerializerStruct{})); err != nil {

 * <p>
 * Qualifiers are used to distinguish between multiple beans of the same type,
 * allowing for more precise control over which implementation should be injected.
 * Custom qualifier annotations should be annotated with {@code @Qualifier}.
 * <p>
 * Example of creating a custom qualifier:
 * <pre>
 * {@literal @}Qualifier
 * {@literal @}Retention(RUNTIME)
 * public @interface Database {
 *     String value();
 * }
 * </pre>
 *

        "czech_analyzer": {
          "type": "custom",
          "tokenizer": "standard",
          "filter": [
            "truncate20_filter",
            "lowercase",
            "czech_stop",
            "czech_keywords",
            "czech_override",
            "czech_stemmer"
          ]
        },
        "danish_analyzer": {
          "type": "custom",
          "tokenizer": "standard",

        "czech_analyzer": {
          "type": "custom",
          "tokenizer": "standard",
          "filter": [
            "truncate20_filter",
            "lowercase",
            "czech_stop",
            "czech_keywords",
            "czech_override",
            "czech_stemmer"
          ]
        },
        "danish_analyzer": {
          "type": "custom",
          "tokenizer": "standard",

# 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:

To add metadata to your OpenAPI schema, including a license, version, contact, etc, read the docs for [Tutorial - Metadata and Docs URLs](../tutorial/metadata.md){.internal-link target=_blank}.

## OpenAPI Custom URL { #openapi-custom-url }

To customize the OpenAPI URL (or remove it), read the docs for [Tutorial - Metadata and Docs URLs](../tutorial/metadata.md#openapi-url){.internal-link target=_blank}.

## OpenAPI Docs URLs { #openapi-docs-urls }

        // Create custom naming convention
        NamingConvention customNamingConvention = new MockNamingConvention() {
            @Override
            public String fromClassNameToComponentName(String className) {
                return super.fromClassNameToComponentName(className);
            }
        };

        // Create PagerCreator with custom naming convention