public BuildResumptionData(final List<String> remainingProjects) {
        this.remainingProjects = remainingProjects;
    }

    /**
     * Returns the projects that still need to be built when resuming.
     * @return A list containing the group and artifact id of the projects.
     */
    public List<String> getRemainingProjects() {
        return this.remainingProjects;
    }

```Python
say_hi()  # Oh, no, this throws an error! 😱
```

The `name` parameter is **still required** (not *optional*) because it doesn't have a default value. Still, `name` accepts `None` as the value:

```Python
say_hi(name=None)  # This works, None is valid 🎉
```

Example:
```
# The Elasticsearch instance to use for all your queries.
elasticsearch.url: "http://localhost:9201"
```

#### Q. I imported "fess\_log.ndjson" but no results found.

Still, in both situations, chances are that **FastAPI** will [still be faster](index.md#performance){.internal-link target=_blank} than (or at least comparable to) your previous framework.

### Dependencies { #dependencies }

        assertNull(originalAfterWipe, "Original password should be null after wipe");
        assertNotNull(clonedAfterWipe, "Cloned password should still exist");
        assertArrayEquals("originalPassword".toCharArray(), clonedAfterWipe, "Cloned password should still have original value");
    }

    @Test
    public void testEqualsWithPassword() {

    for (LoadingCache<Object, Object> cache : caches()) {
      cache.getUnchecked(1);
      cache.getUnchecked(2);

      Set<Object> keys = cache.asMap().keySet();
      // We don't know whether these are still in the cache, so we can't assert on the return
      // values of these removes, but the cache should be empty after the removes, regardless.
      keys.remove(1);
      keys.remove(2);

    for (LoadingCache<Object, Object> cache : caches()) {
      cache.getUnchecked(1);
      cache.getUnchecked(2);

      Set<Object> keys = cache.asMap().keySet();
      // We don't know whether these are still in the cache, so we can't assert on the return
      // values of these removes, but the cache should be empty after the removes, regardless.
      keys.remove(1);
      keys.remove(2);

        // Should write command byte + null terminator only
        assertEquals(2, used, "Null path should result in command byte + NUL");
        assertEquals(0x04, buffer[0] & 0xFF, "First byte must still be 0x04");
        assertEquals(0, buffer[1], "Second byte must be null terminator");
    }

    @Test
    @DisplayName("writeBytesWireFormat handles empty string gracefully")
    void testWriteEmptyString() {

        assertEquals(1, pairs.size(), "Should start with 1 pair");

        AvPairs.remove(pairs, AvPair.MsvAvFlags);

        assertEquals(1, pairs.size(), "Should still have 1 pair");
        assertTrue(AvPairs.contains(pairs, AvPair.MsvAvTimestamp), "Should still contain MsvAvTimestamp");
    }

    /**
     * Test replace method
     */
    @Test
    @DisplayName("Replace should remove old and add new")

And all the ideas in the section about [adding `dependencies` to the *path operation decorators*](dependencies-in-path-operation-decorators.md){.internal-link target=_blank} still apply, but in this case, to all of the *path operations* in the app.

## Dependencies for groups of *path operations* { #dependencies-for-groups-of-path-operations }