boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

                return true;
            }
            return false;
        }

        /**
         * Checks if the given day is included in this rule's applicable days.
         *
         * @param day the day of the week (1=Sunday, 7=Saturday)
         * @return true if the day is included, false otherwise
         */
        private boolean isInDays(final int day) {
            if (days.length == 0) {

      while (iterator.hasNext()) {
        Class<?> current = iterator.next();
        if (current == itf || itf.isAssignableFrom(current)) {
          // Skip any super interface of the ones that are already included.
          addToSet = false;
          break;
        }
      }
      if (addToSet) {
        interfaceClasses.add(itf);
      }
    }
    // Make the proxy serializable to work with SerializableTester

  build1 --> project2
  
  build2["included build"]
  build_tree --> build2
  
  project3["root project"]
  build2 --> project3
  
  project4["project"]
  build2 --> project4

```

### Build process state

The "build process state" holds the global state of the build process and manages all the other state.

The build process state also includes state that is tied to a particular Gradle user home directory.

      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

            cmdList.add("-D" + name + "=" + defaultValue);
        }
    }

    /**
     * Adds all Fess configuration properties to the command list.
     * Properties starting with the Fess config prefix are included.
     *
     * @param cmdList the command list to add properties to
     */
    protected void addFessConfigProperties(final List<String> cmdList) {
        System.getProperties()
                .keySet()

This is an advanced usage that you might not really need, but it's there in case you do.

## Include an `APIRouter` in another { #include-an-apirouter-in-another }

The same way you can include an `APIRouter` in a `FastAPI` application, you can include an `APIRouter` in another `APIRouter` using:

```Python
router.include_router(other_router)
```

  <suppress files="modules[/\\]lang-painless[/\\]src[/\\]test[/\\]java[/\\]org[/\\]elasticsearch[/\\]painless[/\\]ContextExampleTests.java" checks="LineLength" />

  <!--
    Truly temporary suppressions suppression of snippets included in
    documentation that are so wide that they scroll.
  -->

	ARR                                   // -> Used on ARM for shift type 3, arithmetic right shift.
	ROT                                   // @> Used on ARM for shift type 4, rotate right.
	Include                               // included file started here
	BuildComment                          // //go:build or +build comment
	macroName                             // name of macro that should not be expanded
)

      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.