*
 * @author David Beaumont
 */
@GwtCompatible
@NullUnmarked
final class UrlEscaperTesting {
  /**
   * Helper to assert common expected behaviour of uri escapers. You should call
   * assertBasicUrlEscaper() unless the escaper explicitly does not escape '%'.
   */
  @SuppressWarnings("nullness") // test of a bogus call

Caching
=======

OkHttp implements an optional, off by default, Cache. OkHttp aims for RFC correct and
pragmatic caching behaviour, following common real-world browser like Firefox/Chrome and
server behaviour when ambiguous.

# Basic Usage

```kotlin
  private val client: OkHttpClient = OkHttpClient.Builder()
      .cache(Cache(
          directory = File(application.cacheDir, "http_cache"),
          // $0.05 worth of phone storage in 2020

 *
 * @author David Beaumont
 */
@GwtCompatible
@NullUnmarked
final class UrlEscaperTesting {
  /**
   * Helper to assert common expected behaviour of uri escapers. You should call
   * assertBasicUrlEscaper() unless the escaper explicitly does not escape '%'.
   */
  @SuppressWarnings("nullness") // test of a bogus call

### Examples

Use American English spelling, for example:

* `color` (not `colour`)
* `initialize` (not `initialise`)
* `behavior` (not `behaviour`)
* `analyze` (not `analyse`)
* `organization` (not `organisation`)
* `center` (not `centre`)
* `canceled` (not `cancelled`)
* `labeled` (not `labelled`)

### Rationale for American English

    assertThrows(
        IllegalArgumentException.class,
        () -> COMMA_SPLITTER.withKeyValueSeparator("=").split("a=1,b,c=2"));
  }

  /**
   * Testing the behavior in https://github.com/google/guava/issues/1900 - this behavior may want to
   * be changed?
   */
  public void testMapSplitter_extraValueDelimiter() {
    assertThrows(
        IllegalArgumentException.class,

 *
 * <h3>Handling of non-finite values</h3>
 *
 * <p>If any values in the input are {@link Double#NaN NaN} then all values returned are {@link
 * Double#NaN NaN}. (This is the one occasion when the behaviour is not the same as you'd get from
 * sorting with {@link java.util.Arrays#sort(double[]) Arrays.sort(double[])} or {@link
 * java.util.Collections#sort(java.util.List) Collections.sort(List&lt;Double&gt;)} and selecting

- Client-go: default informer behavior now updates store state with all the objects in a list or relist, before calling...

    `LSTMStateTuple`. The new behavior leads to proper dropout behavior for
    LSTMs and stacked LSTMs. This bug fix follows recommendations from published
    literature, but is a behavioral change. State dropout behavior may be
    customized via the new `dropout_state_filter_visitor` argument.
*   Removed `tf.contrib.training.python_input`. The same behavior, in a more

  To request this behaviour, your client software must enable the `WatchListClient` client-go feature gate. Additionally, streaming is only available if supported by the cluster; the API server that you connect to must also support streaming.

### Do's
1. Use `@Resource` for field injection (not constructor injection)
2. Access helpers via `ComponentUtil.getXyzHelper()`
3. Use `OptionalEntity<T>` for nullable entity returns
4. Use DBFlute behavior classes (Bhv) for data access
5. Put user-facing strings in `fess_label_*.properties`
6. Run `mvn formatter:format` and `mvn license:format` before committing

### Don'ts