*
     * @param form the create form
     * @param username the current username
     * @param currentTime the current time
     * @return optional label type entity
     */
    public static OptionalEntity<LabelType> getEntity(final CreateForm form, final String username, final long currentTime) {
        switch (form.crudMode) {
        case CrudMode.CREATE:

```Python
UserInDB(**user_dict)
```

다음과 같은 결과를 생성합니다:

```Python
UserInDB(
    username="john",
    password="secret",
    email="******@****.***",
    full_name=None,
)
```

혹은 더 정확히 말하자면, `user_dict`를 직접 사용하는 것은, 나중에 어떤 값이 추가되더라도 아래와 동일한 효과를 냅니다:

```Python
UserInDB(
    username = user_dict["username"],
    password = user_dict["password"],
    email = user_dict["email"],

     | a unique name within the system (referred to by the 'id' attribute below).
     |
     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
     |       used together.
     |
    <server>
      <id>deploymentRepo</id>
      <username>repouser</username>
      <password>repopwd</password>
    </server>
    -->

    <!-- Another sample, using keys to authenticate.

Nie wieder falsche Schlüsselnamen tippen, Hin und Herhüpfen zwischen der Dokumentation, Hoch- und Runterscrollen, um herauszufinden, ob es `username` oder `user_name` war.

### Kompakt { #short }

    listOf(
        "-Porg.gradle.performance.branchName" to "%teamcity.build.branch%",
        "-Porg.gradle.performance.db.url" to "%performance.db.url%",
        "-Porg.gradle.performance.db.username" to "%performance.db.username%",
    ).map { (key, value) -> os.escapeKeyValuePair(key, value) }

const val INDIVIDUAL_PERFORAMCE_TEST_ARTIFACT_RULES = """
testing/*/build/test-results-*.zip => results

Zum Beispiel stellt eine der Möglichkeiten, die OAuth2-Spezifikation zu verwenden (genannt „password flow“), die Bedingung, einen `username` und ein `password` als Formularfelder zu senden.

Die <dfn title="Spezifikation">Spezifikation</dfn> erfordert, dass die Felder exakt `username` und `password` genannt werden und als Formularfelder, nicht JSON, gesendet werden.

Но вы не ограничены использованием какой-то конкретной модели данных, класса или типа.

Хотите, чтобы в модели были `id` и `email`, но не было `username`? Пожалуйста. Можно использовать те же инструменты.

Хотите просто `str`? Или просто `dict`? Или напрямую экземпляр класса модели базы данных? Всё работает одинаково.

    /**
     * The protocol scheme (http, https).
     */
    @Size(max = 10)
    public String protocolScheme;

    /**
     * The username for authentication.
     */
    @Required
    @Size(max = 100)
    public String username;

    /**
     * The password for authentication.
     */
    @Size(max = 100)
    public String password;

    /**

    /** The protocol scheme for file access (maximum 10 characters). */
    @Size(max = 10)
    public String protocolScheme;

    /** The username for file authentication (required, maximum 100 characters). */
    @Required
    @Size(max = 100)
    public String username;

    /** The password for file authentication (maximum 100 characters). */
    @Size(max = 100)
    public String password;

    private static final String DOMAIN = Config.getProperty("jcifs.smb1.smb.client.domain", null);
    private static final String USERNAME = Config.getProperty("jcifs.smb1.smb.client.username", null);
    private static final int CACHE_POLICY = Config.getInt("jcifs.smb1.netbios.cachePolicy", 60 * 10) * 60; /* 10 hours */

    static NbtAddress[] dc_list = null;