<a href="https://www.greptile.com/?utm_source=fastapi&utm_medium=sponsorship&utm_campaign=fastapi_sponsor_page" target="_blank" title="Greptile: The AI Code Reviewer"><img src="https://fastapi.tiangolo.com/img/sponsors/greptile.png"></a>

platforms/documentation/docs/src/docs/userguide/reference/core-plugins/checkstyle_plugin.adoc           @gradle/bt-docs-reviewers @gradle/bt-jvm
platforms/documentation/docs/src/docs/userguide/reference/core-plugins/codenarc_plugin.adoc             @gradle/bt-docs-reviewers @gradle/bt-jvm
platforms/documentation/docs/src/docs/userguide/reference/core-plugins/distribution_plugin.adoc         @gradle/bt-docs-reviewers @gradle/bt-jvm

* 🔨 Verify `mkdocs.yml` languages in CI, update `docs.py`. PR [#11009](https://github.com/tiangolo/fastapi/pull/11009) by [@tiangolo](https://github.com/tiangolo).
* 🔧 Update config in `label-approved.yml` to accept translations with 1 reviewer. PR [#11007](https://github.com/tiangolo/fastapi/pull/11007) by [@alejsdev](https://github.com/alejsdev).

permissions: {}

jobs:
  add-reviews:
    permissions:
      contents: read  # for kentaro-m/auto-assign-action to fetch config file
      pull-requests: write  # for kentaro-m/auto-assign-action to assign PR reviewers
    runs-on: ubuntu-latest
    steps:

There are hundreds of other contributors, you can see them all in the [FastAPI GitHub Contributors page](https://github.com/fastapi/fastapi/graphs/contributors). 👷

## Top Translation Reviewers

These users are the **Top Translation Reviewers**. 🕵️

Translation reviewers have the [**power to approve translations**](contributing.md#translations) of the documentation. Without them, there wouldn't be documentation in several other languages.

        // Test with multiple roles
        testUser.setRoleNames(new String[] { "admin", "user", "manager" });
        assertTrue(fessUserBean.hasRoles(new String[] { "admin" }));
        assertTrue(fessUserBean.hasRoles(new String[] { "user", "guest" }));
        assertTrue(fessUserBean.hasRoles(new String[] { "manager", "viewer" }));

* To avoid asking the same thing multiple times during code review.
* To explain *rejected solutions*, for now, and future development, in case they are proposed again.

ADRs can be written by any team.
Like code, they should be reviewed by any other relevant teams.
The goal is not to *own* a decision, but to *share* it with other teams, and improve the build tool together.

### Format

The format for ADR should follow this template:

```markdown

* **Documentation**: Documentation should be updated to use American English, prioritizing user-facing documentation

* During code reviews that introduce new APIs, reviewers need to be mindful that all new properties are implemented with lazy types.

        String[] roles = secured.value();
        assertNotNull(roles);
        assertEquals(0, roles.length);
    }

    // Test with special characters in roles
    @Secured({ "ROLE_USER-ADMIN", "ROLE_USER.VIEWER", "ROLE_USER_EDITOR", "ROLE$SPECIAL" })
    static class SpecialCharacterRolesClass {
    }

    @Test
    public void test_specialCharactersInRoles() {