data.mappings.escapeDataString(),
        ).build(),
    ).build()
}

/**
 * KotlinPoet doesn't really know what to do with a string containing NUL, BEL, DEL, etc. We also
 * don't want to perform `trimMargin()` at runtime.
 */
fun String.escapeDataString(): String =
  buildString {
    for (codePoint in ******@****.***ints()) {
      when (codePoint) {
        in 0..0x20,

import org.jspecify.annotations.Nullable;

/**
 * A callback interface to process bytes from a stream.
 *
 * <p>{@link #processBytes} will be called for each chunk of data that is read, and should return
 * {@code false} when you want to stop processing.
 *
 * @author Chris Nokleberg
 * @since 1.0
 */
@DoNotMock("Implement it normally")
@J2ktIncompatible
@GwtIncompatible
public interface ByteProcessor<T extends @Nullable Object> {
  /**

    "nullness", // test of a bogus call
  })
  public void testRepeat_null() {
    assertThrows(NullPointerException.class, () -> Strings.repeat(null, 5));
  }

  @SuppressWarnings("UnnecessaryStringBuilder") // We want to test a non-String CharSequence
  public void testCommonPrefix() {
    assertThat(Strings.commonPrefix("", "")).isEqualTo("");
    assertThat(Strings.commonPrefix("abc", "")).isEqualTo("");

 * </ul>
 *
 * <p>The main purpose of {@link #addListener addListener} is to support this chaining. You will
 * rarely use it directly, in part because it does not provide direct access to the {@code Future}
 * result. (If you want such access, you may prefer {@link Futures#addCallback
 * Futures.addCallback}.) Still, direct {@code addListener} calls are occasionally useful:
 *
 * {@snippet :
 * final String name = ...;
 * inFlight.add(name);

        if (configExists() && !force) {
            context.logger.error(messageBuilderFactory
                    .builder()
                    .error("Error: configuration exist. Use --force if you want to reset existing configuration.")
                    .build());
            return BAD_OPERATION;
        }

        context.addInHeader(context.style.italic().bold().foreground(Colors.rgbColor("yellow")), "goal: init");

<img src="/img/tutorial/additional-responses/image01.png">

## Combine predefined responses and custom ones { #combine-predefined-responses-and-custom-ones }

You might want to have some predefined responses that apply to many *path operations*, but you want to combine them with custom responses needed by each *path operation*.

For those cases, you can use the Python technique of "unpacking" a `dict` with `**dict_to_unpack`:

```Python

This way, you don't have to know beforehand what the valid field/attribute names are (as would be the case with Pydantic models).

This would be useful if you want to receive keys that you don't already know.

---

Another useful case is when you want to have keys of another type (e.g., `int`).

That's what we are going to see here.

import java.util.ArrayList;
import java.util.List;
import java.util.Locale;
import java.util.stream.Collectors;

import static java.util.Arrays.asList;
import static java.util.Arrays.stream;

/**
 * We want to be able to do BWC tests for unreleased versions without relying on and waiting for snapshots.
 * For this we need to check out and build the unreleased versions.

        Artifact artifact = request.getArtifact();

        //
        // If we have a system scoped artifact, then we do not want any searching in local or remote repositories,
        // and we want artifact resolution to only return the system scoped artifact itself.
        //
        if (artifact.getScope() != null && artifact.getScope().equals(Artifact.SCOPE_SYSTEM)) {

        with:
          results_file: results.sarif
          results_format: sarif
          # (Optional) "write" PAT token. Uncomment the `repo_token` line below if:
          # - you want to enable the Branch-Protection check on a *public* repository, or
          # - you are installing Scorecard on a *private* repository