/** The parameter for exact phrase query. */
    public static final String AS_EPQ = "epq";

    /** The parameter for query. */
    public static final String AS_Q = "q";

    /** The parameter for filetype. */
    public static final String AS_FILETYPE = "filetype";

    /** The parameter for sitesearch. */
    public static final String AS_SITESEARCH = "sitesearch";

    /** The parameter for occurrence. */

                return null;
            }
        };

        // Test with string parameter
        Map<String, Object> stringParams = new HashMap<>();
        stringParams.put("string", "test");
        assertNotNull(queryRescorer.evaluate(stringParams));

        // Test with number parameter
        Map<String, Object> numberParams = new HashMap<>();
        numberParams.put("number", 123);

            assertHasErrors(
                "Field nonFinalField: Nullability breaking change.",
                "Method com.example.Source.foo(java.lang.String): Parameter 0 from null accepting to non-null accepting breaking change.",
                "Constructor com.example.Source(java.lang.String): Parameter 0 from null accepting to non-null accepting breaking change."
            )
            assertHasNoWarning()
            assertHasNoInformation()
        }

    public void setParameters(List<Parameter> parameters) throws DuplicateParameterException {
        this.parameters.clear();
        for (Parameter parameter : parameters) {
            addParameter(parameter);
        }
    }

    /**
     * @param parameter add a new parameter
     * @throws DuplicateParameterException if any
     */
    public void addParameter(Parameter parameter) throws DuplicateParameterException {

/// tip

Some editors check for unused function parameters, and show them as errors.

Using these `dependencies` in the *path operation decorator* you can make sure they are executed while avoiding editor/tooling errors.

It might also help avoid confusion for new developers that see an unused parameter in your code and could think it's unnecessary.

///

/// info

class MojoDescriptorTest {
    @Test
    void getParameterMap() throws DuplicateParameterException {
        MojoDescriptor mojoDescriptor = new MojoDescriptor();
        Parameter param1 = new Parameter();
        param1.setName("param1");
        param1.setDefaultValue("value1");
        mojoDescriptor.addParameter(param1);

        assertEquals(1, mojoDescriptor.getParameters().size());

            throw new IORuntimeException(e);
        }
    }

    /**
     * Parses request parameters from a string.
     * @param params The parameter string.
     * @param paramList Additional parameters.
     * @param encoding The encoding.
     * @return The HttpEntity containing the parsed parameters.
     */

    }

    /**
     * Gets the extra parameters for provider-specific settings.
     *
     * @return the extra parameters map, or {@code null} if not set
     */
    public Map<String, String> getExtraParams() {
        return extraParams;
    }

    /**
     * Sets the extra parameters for provider-specific settings.
     *
     * @param extraParams the extra parameters map

{* ../../docs_src/dependencies/tutorial005_an_py310.py hl[13] *}

Let's focus on the parameters declared:

* Even though this function is a dependency ("dependable") itself, it also declares another dependency (it "depends" on something else).
    * It depends on the `query_extractor`, and assigns the value returned by it to the parameter `q`.
* It also declares an optional `last_query` cookie, as a `str`.

# Path Operation Configuration { #path-operation-configuration }

There are several parameters that you can pass to your *path operation decorator* to configure it.

/// warning

Notice that these parameters are passed directly to the *path operation decorator*, not to your *path operation function*.

///

## Response Status Code { #response-status-code }

You can define the (HTTP) `status_code` to be used in the response of your *path operation*.