When you declare other function parameters that are not part of the path parameters, they are automatically interpreted as "query" parameters.

{* ../../docs_src/query_params/tutorial001_py310.py hl[9] *}

The query is the set of key-value pairs that go after the `?` in a URL, separated by `&` characters.

For example, in the URL:

```
http://127.0.0.1:8000/items/?skip=0&limit=10
```

...the query parameters are:

	if target.sendErr {
		return errors.New("send error")
	}

	return nil
}

// SendFromStore - interface compatible method does no-op.
func (target *ExampleTarget) SendFromStore(_ store.Key) error {
	return nil
}

func (target ExampleTarget) Close() error {
	if target.closeErr {
		return errors.New("close error")
	}

	return nil
}

func (target ExampleTarget) IsActive() (bool, error) {

### コールバックのパス式 { #the-callback-path-expression }

コールバックの *パス* には、*あなたの API* に送られた元のリクエストの一部を含められる [OpenAPI 3 の式](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#key-expression)を使用できます。

この例では、`str` は次のとおりです:

```Python
"{$callback_url}/invoices/{$request.body.id}"

            .header("Upgrade", "websocket")
            .header("Sec-WebSocket-Key", "abc123")
            .build(),
        ).execute()
    response.body.close()
    networkLogs
      .assertLogEqual("--> GET $url http/1.1")
      .assertLogEqual("Connection: Upgrade")
      .assertLogEqual("Upgrade: websocket")
      .assertLogEqual("Sec-WebSocket-Key: abc123")
      .assertLogEqual("Host: $host")

        assertEquals(oomCause, oomException.getCause());
    }

    @Test
    public void test_messageCodeWithPropertyKey() {
        // Setup - test message code with different property keys
        final String message = "Query field error";
        final String propertyKey = "searchQuery";
        final VaMessenger<FessMessages> messageCode = messages -> messages.addErrorsInvalidQueryUnknown(propertyKey);

      const val BOUNCYCASTLE_PROPERTY = "bouncycastle"
      const val LOOM_PROPERTY = "loom"

      /**
       * For whatever reason our BouncyCastle provider doesn't work with ECDSA keys. Just configure it
       * to use RSA-2048 instead.
       *
       * (We otherwise prefer ECDSA because it's faster.)
       */

      <li><a href="https://maven.apache.org/xsd/maven-4.1.0.xsd">https://maven.apache.org/xsd/maven-4.1.0.xsd</a> for Maven 4.</li>
    </ul>
    ]]>
  </description>
  <defaults>
    <default>
      <key>package</key>
      <value>org.apache.maven.model</value>
    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="project">
      <name>Model</name>
      <superClass>ModelBase</superClass>

  - `--service-account-key-file`, set to one or more files containing one or more public keys used to verify tokens.

        inner.put("key", "value");
        final Map<String, Object> outer = new LinkedHashMap<>();
        outer.put("inner", inner);
        source.put("nested", outer);

        final String json = new JsonIndexExportFormatter().format(source, Collections.emptySet());

        assertTrue(json.contains("\"nested\": {\"inner\": {\"key\": \"value\"}}"));
    }

    @Test

            BuildPlanExecutor.attachToThread(step.project);
            session.setCurrentProject(step.project);
        }

        private Clock getClock(Object key) {
            return clocks.computeIfAbsent(key, p -> new Clock());
        }

        private void plan() {
            lock.writeLock().lock();
            try {
                Set<BuildStep> planSteps = plan.allSteps()