code is a great way to give something back to the open source community. Before
you dig right into the code, there are a few guidelines that we need
contributors to follow so that we can have a chance of keeping on top of
things.

Some of the ideas are documented in the [Maven Wiki][maven-wiki]
which might be interesting to read and for further discussion.

Getting Started
---------------

        logger.debug(indent + artifact + " (not setting artifactScope to: " + ignoredScope + "; local artifactScope "
                + artifact.getScope() + " wins)");

        // TODO better way than static? this might hide messages in a reactor
        if (!ignoredArtifacts.contains(artifact)) {
            logger.warn("\n\tArtifact " + artifact + " retains local artifactScope '" + artifact.getScope()

        + WRAPPER_VERSION + "/maven-wrapper-" + WRAPPER_VERSION + ".jar";

    /**
     * Path to the maven-wrapper.properties file, which might contain a downloadUrl property to
     * use instead of the default one.
     */
    private static final String MAVEN_WRAPPER_PROPERTIES_PATH =
            ".mvn/wrapper/maven-wrapper.properties";

    /**

        try {
            String[] languages = searchHelper.getLanguages(getMockRequest(), params);

            assertNotNull(languages);
            if (languages.length > 0) {
                // Note: The actual order might be different due to normalization
                boolean hasEn = false, hasJa = false;
                for (String lang : languages) {
                    if ("en".equals(lang))
                        hasEn = true;

The whole **FastAPI** framework is based to satisfy that. Autocompletion works everywhere.

You will rarely need to come back to the docs.

Here's how your editor might help you:

* in <a href="https://code.visualstudio.com/" class="external-link" target="_blank">Visual Studio Code</a>:

![editor support](https://fastapi.tiangolo.com/img/vscode-completion.png)

	case reflect.Float32, reflect.Float64:
		return true
	default:
		return false
	}
}

// ExplainSQL generate SQL string with given parameters, the generated SQL is expected to be used in logger, execute it might introduce a SQL injection vulnerability
func ExplainSQL(sql string, numericPlaceholder *regexp.Regexp, escaper string, avars ...interface{}) string {
	var (
		convertParams func(interface{}, int)

 *       href="https://github.com/google/guava/issues/6126#issuecomment-1204399671">treats it
 *       identically to {@code Nullable}</a> as of version 0.9.9.
 *   <li><a href="https://developers.google.com/j2objc">J2ObjC</a>, maybe: It might no longer be
 *       necessary there, since we have stopped using the {@code @ParametersAreNonnullByDefault}
 *       annotations that {@code ParametricNullness} was counteracting.
 * </ul>
 *

 *       href="https://github.com/google/guava/issues/6126#issuecomment-1204399671">treats it
 *       identically to {@code Nullable}</a> as of version 0.9.9.
 *   <li><a href="https://developers.google.com/j2objc">J2ObjC</a>, maybe: It might no longer be
 *       necessary there, since we have stopped using the {@code @ParametersAreNonnullByDefault}
 *       annotations that {@code ParametricNullness} was counteracting.
 * </ul>
 *

 *       href="https://github.com/google/guava/issues/6126#issuecomment-1204399671">treats it
 *       identically to {@code Nullable}</a> as of version 0.9.9.
 *   <li><a href="https://developers.google.com/j2objc">J2ObjC</a>, maybe: It might no longer be
 *       necessary there, since we have stopped using the {@code @ParametersAreNonnullByDefault}
 *       annotations that {@code ParametricNullness} was counteracting.
 * </ul>
 *

 * such custom interfaces directly; they are implemented only in subclasses. Therefore, forwarding
 * {@code equals} would break symmetry, as the forwarding object might consider itself equal to the
 * object being tested, but the reverse could not be true. This behavior is consistent with the
 * JDK's collection wrappers, such as {@link java.util.Collections#unmodifiableCollection}. Use an