Inconsistency in spelling conventions can lead to several issues:

* **Confusion for users and contributors**: Mixed spellings (e.g., "color" and "colour", "initialize" and "initialise") in the codebase create confusion about which variant to use
* **Harder code search and refactoring**: Searching for identifiers, method names, or documentation becomes more difficult when multiple spellings exist for the same concept

#### Merging pull requests ####

Due to Guava's nature as a subset of Google's internal codebase which is
automatically synced to the public GitHub repository, we are unable to merge
pull requests directly into the master branch. Instead, once a pull request is
ready for merging, we'll make the appropriate changes in the internal codebase
and, when the change is synced out, give the pull request author credit for the
commit.

# ADR-0008 - Use NullAway for null checking

## Date

2025-08-06

## Context

Our codebase uses `null` extensively to represent an absence of value or optionality of the argument.
We utilize nullness annotations in Java code and somewhat rely on IDE warnings to guide us.
However, the Java code we have is not fully annotated, which causes several consequences:
* IDE warnings can be misleading

# Maintenance Mode

**This project is currently under maintenance and is not accepting new changes.**

- The codebase is in a maintenance-only state
- No new features, enhancements, or pull requests will be accepted
- Critical security fixes may be evaluated on a case-by-case basis
- Existing issues and pull requests will not be actively reviewed
- Community support continues on a best-effort basis through [Slack](https://slack.min.io)

                    }
                }
            }
        }
        return commonRoot;
    }

    /**
     * Writes a Document to a file using the same format as the existing codebase.
     */
    private void writePomToFile(Document document, Path filePath) throws Exception {
        Files.writeString(filePath, document.toXml());
    }

    /**

                && profile.getPluginRepositories().isEmpty()
                && profile.getReporting() == null;
    }

    private static <T extends ModelBase.Builder> T prune(T builder, ModelBase model) {
        builder.properties(null).reporting(null);
        if (model.getDistributionManagement() != null
                && model.getDistributionManagement().getRelocation() != null) {

            buf.append(' ').append(fileName);
        }
        final String bodyBase = buf.toString().trim();
        responseData.addMetaData(Extractor.class.getSimpleName(), extractor);
        final String body = documentHelper.getContent(crawlingConfig, responseData, bodyBase, dataMap);
        putResultDataBody(dataMap, fessConfig.getIndexFieldContent(), body);

One of the **biggest benefits** is that now you can create `Annotated` dependencies that are then shared by multiple *path operation functions*, this will allow you to **reduce** a lot of **code duplication** in your codebase, while keeping all the support from editors and tools.

For example, you could have code like this:

```Python
def get_current_user(token: str):
    # authenticate user
    return User()

... denn es ist nicht klar, ob der Defaultwert `"rick"` oder `"morty"` sein soll.

Sie würden also (bevorzugt) schreiben:

```Python
q: Annotated[str, Query()] = "rick"
```

... oder in älteren Codebasen finden Sie:

```Python
q: str = Query(default="rick")
```

### Vorzüge von `Annotated` { #advantages-of-annotated }

      <key>package</key>
      <value>org.apache.maven.model</value>
    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="project">
      <name>Model</name>
      <superClass>ModelBase</superClass>
      <description>
        The {@code &lt;project>} element is the root of the descriptor.
        The following table lists all of the possible child elements.
      </description>