@NullUnmarked
public class InvokableTest extends TestCase {
  // Historically Invokable inherited from java.lang.reflect.AccessibleObject. That's no longer the
  // case, but we do check that its API still has the same public methods. We exclude some methods
  // that were added in Java 9 and that people probably weren't calling via Invokable, namely
  // `boolean canAccess(Object)`.
  public void testApiCompatibleWithAccessibleObject() {

В документации это будет показано так:

<img src="/img/tutorial/query-params-str-validations/image01.png">

## Исключить параметры из OpenAPI { #exclude-parameters-from-openapi }

Чтобы исключить query-параметр из генерируемой OpenAPI-схемы (и, следовательно, из систем автоматической документации), укажите у `Query` параметр `include_in_schema=False`:

     * This method evaluates all configured query rescorers with the provided parameters.
     *
     * @param params parameters to pass to the rescorers during evaluation
     * @return an array of rescorer builders, filtered to exclude null values
     */
    public RescorerBuilder<?>[] getRescorers(final Map<String, Object> params) {

	for i, b := range h.QueuedBuckets {
		if b == bucket {
			// Delete...
			h.QueuedBuckets = append(h.QueuedBuckets[:i], h.QueuedBuckets[i+1:]...)
		}
	}
}

// setQueuedBuckets will add buckets, but exclude any that is already in h.HealedBuckets.
// Order is preserved.
func (h *healingTracker) setQueuedBuckets(buckets []BucketInfo) {
	h.mu.Lock()
	defer h.mu.Unlock()

	s := set.CreateStringSet(h.HealedBuckets...)

Die Dokumentation wird es so anzeigen:

<img src="/img/tutorial/query-params-str-validations/image01.png">

## Parameter von OpenAPI ausschließen { #exclude-parameters-from-openapi }

Um einen Query-Parameter aus dem generierten OpenAPI-Schema auszuschließen (und somit aus den automatischen Dokumentationssystemen), setzen Sie den Parameter `include_in_schema` von `Query` auf `False`:

          <version>4.0.0+</version>
          <description>The group ID of the project to exclude.</description>
          <type>String</type>
          <required>true</required>
        </field>
        <field>
          <name>artifactId</name>
          <version>4.0.0+</version>
          <description>The artifact ID of the project to exclude.</description>
          <type>String</type>
          <required>true</required>

     * Excludes the active session and optionally filters by name.
     * This method performs batch deletion of both parameters and session records.
     *
     * @param activeSessionId the session ID to exclude from deletion (can be null)
     * @param name optional name filter for sessions to delete (can be null or blank)
     * @param date the expiration time threshold - sessions expired before this time will be deleted
     */

            int consumed = 15; // reqPath.length() = 15

            DfsReferralDataImpl result = DfsReferralDataImpl.fromReferral(mockReferral, reqPath, expire, consumed);

            // Should have adjusted pathConsumed to exclude trailing slash
            assertEquals(14, result.getPathConsumed());
        }

        @ParameterizedTest

///

## Type Hints com Metadados de Anotações { #type-hints-with-metadata-annotations }

O Python possui uma funcionalidade que nos permite incluir **<abbr title="Informação sobre a informação, neste caso, informação sobre o tipo, e.g. uma descrição.">metadados</abbr> adicionais** nos type hints utilizando `Annotated`.

Hasta aquí, todo funcionaría normalmente.