ModelProblemCollector problems,
            Severity severity,
            Version version,
            String scope,
            String sourceHint,
            InputLocationTracker tracker,
            boolean isDependencyManagement) {
        if (scope == null || scope.length() <= 0) {
            return true;
        }

        String[] validScopes;
        if (isDependencyManagement) {

/// note | Technical Details

A `Request` has a `request.scope` attribute, that's just a Python `dict` containing the metadata related to the request.

A `Request` also has a `request.receive`, that's a function to "receive" the body of the request.

The `scope` `dict` and `receive` function are both part of the ASGI specification.

And those two things, `scope` and `receive`, are what is needed to create a new `Request` instance.

        lenient().when(mockConfig.getNetbiosScope()).thenReturn("DEFAULT.SCOPE");
        lenient().when(mockConfig.getOemEncoding()).thenReturn("UTF-8");

        // Setup mock name
        lenient().when(mockName.writeWireFormat(any(byte[].class), anyInt())).thenReturn(34);
        mockName.hexCode = 0x20;
        mockName.name = "TEST";
        mockName.scope = "test.scope";
    }

    @Test

            @Nonnull Project project,
            @Nonnull ProjectScope scope,
            @Nonnull Language language,
            @Nonnull Path directory) {
        MavenProject prj = getMavenProject(requireNonNull(project, "project" + " cannot be null"));
        prj.addSourceRoot(
                requireNonNull(scope, "scope" + " cannot be null"),
                requireNonNull(language, "language" + " cannot be null"),

import org.eclipse.aether.internal.impl.scope.ManagedDependencyContextRefiner;
import org.eclipse.aether.internal.impl.scope.ManagedScopeDeriver;
import org.eclipse.aether.internal.impl.scope.ManagedScopeSelector;
import org.eclipse.aether.internal.impl.scope.OptionalDependencySelector;
import org.eclipse.aether.internal.impl.scope.ScopeDependencySelector;
import org.eclipse.aether.internal.impl.scope.ScopeManagerImpl;

    }

    private ArtifactSpec createArtifactSpec(String id, String version, String scope)
            throws InvalidVersionSpecificationException {
        return createArtifactSpec(id, version, scope, null, false);
    }

    private ArtifactSpec createArtifactSpec(
            String id, String version, String scope, String inheritedScope, boolean optional)
            throws InvalidVersionSpecificationException {

/// note | Detalhes Técnicos

Um `Request` tem um atributo `request.scope`, que é apenas um `dict` do Python contendo os metadados relacionados à requisição.

Um `Request` também tem um `request.receive`, que é uma função para "receber" o corpo da requisição.

O dicionário `scope` e a função `receive` são ambos parte da especificação ASGI.

E essas duas coisas, `scope` e `receive`, são o que é necessário para criar uma nova instância de `Request`.

			<version>1.3.5</version>
			<optional>true</optional>
		</dependency>
		<dependency>
			<groupId>junit</groupId>
			<artifactId>junit</artifactId>
			<version>4.13.2</version>
			<scope>test</scope>
		</dependency>
	</dependencies>

                            "title": "Password",
                            "type": "string",
                            "format": "password",
                        },
                        "scope": {"title": "Scope", "type": "string", "default": ""},
                        "client_id": {
                            "title": "Client Id",
                            "anyOf": [{"type": "string"}, {"type": "null"}],

### Dependencias con `yield` y `scope` { #dependencies-with-yield-and-scope }

En la versión 0.121.0, FastAPI agregó soporte para `Depends(scope="function")` para dependencias con `yield`.