/**
     * Array of web crawling configuration IDs to process.
     * If null, all available web configurations will be crawled (when no other config IDs are specified).
     */
    protected String[] webConfigIds;

    /**
     * Array of file system crawling configuration IDs to process.
     * If null, all available file configurations will be crawled (when no other config IDs are specified).
     */

But I'll show you how to improve that next. 🤓

## Custom Operation IDs and Better Method Names { #custom-operation-ids-and-better-method-names }

You can **modify** the way these operation IDs are **generated** to make them simpler and have **simpler method names** in the clients.

Pero te mostraré cómo mejorar eso a continuación. 🤓

## Operation IDs personalizados y mejores nombres de métodos { #custom-operation-ids-and-better-method-names }

Puedes **modificar** la forma en que estos operation IDs son **generados** para hacerlos más simples y tener **nombres de métodos más simples** en los clientes.

 *   -n, --name name               : Name for the crawling session
 *   -w, --webConfigIds ids        : Comma-separated web config IDs
 *   -f, --fileConfigIds ids       : Comma-separated file config IDs
 *   -d, --dataConfigIds ids       : Comma-separated data config IDs
 *   -p, --properties path         : Properties file path
 *   -e, --expires days            : Expires for documents (in days)

    }

    /**
     * Retrieves web crawling configurations filtered by a list of IDs.
     * If the ID list is null, returns all available configurations.
     *
     * @param idList the list of configuration IDs to retrieve, or null for all configurations
     * @return a list of WebConfig objects with the specified IDs
     */
    public List<WebConfig> getWebConfigListByIds(final List<String> idList) {

Mas eu vou te mostrar como melhorar isso a seguir. 🤓

## IDs de operação personalizados e nomes de métodos melhores { #custom-operation-ids-and-better-method-names }

Você pode **modificar** a maneira como esses IDs de operação são **gerados** para torná-los mais simples e ter **nomes de método mais simples** nos clientes.

Aber ich zeige Ihnen als Nächstes, wie Sie das verbessern können. 🤓

## Benutzerdefinierte Operation-IDs und bessere Methodennamen { #custom-operation-ids-and-better-method-names }

     * This method retrieves only direct group memberships and collects group IDs for later
     * asynchronous parent group lookup.
     * @param user The Entra ID user.
     * @param groupList The list to add group names to.
     * @param roleList The list to add role names to.
     * @param groupIdsForParentLookup The list to collect group IDs for later parent lookup.
     * @param url The Microsoft Graph API URL.
     */

* media type: media type (do not translate to "tipo de mídia")
* non-Annotated: non-Annotated (do not translate non-Annotated when it comes after a Python version.e.g., “Python 3.10+ non-Annotated”)
* operation IDs: IDs de operação
* path (as in URL path): path
* path operation: operação de rota
* path operation function: função de operação de rota
* prefix: prefixo

app = FastAPI()


@app.get("/items/")
async def read_items():
    return [{"item_id": "Foo"}]


def use_route_names_as_operation_ids(app: FastAPI) -> None:
    """
    Simplify operation IDs so that generated API clients have simpler function
    names.

    Should be called only after all routes have been added.
    """
    for route in app.routes:
        if isinstance(route, APIRoute):