And of course, it supports the same:

* data validation
* data serialization
* data documentation, etc.

This works the same way as with Pydantic models. And it is actually achieved in the same way underneath, using Pydantic.

/// info

After authenticating in the system, you will see it like:

<img src="/img/tutorial/security/image05.png">

### Get your own user data { #get-your-own-user-data }

Now use the operation `GET` with the path `/users/me`.

You will get your user's data, like:

```JSON
{
  "username": "johndoe",
  "email": "******@****.***",
  "full_name": "John Doe",
  "disabled": false,

///

## About "Form Fields" { #about-form-fields }

The way HTML forms (`<form></form>`) sends the data to the server normally uses a "special" encoding for that data, it's different from JSON.

**FastAPI** will make sure to read that data from the right place instead of JSON.

/// note | Technical Details

Data from forms is normally encoded using the "media type" `application/x-www-form-urlencoded`.

                                            <c:forEach var="data" varStatus="s"
                                                       items="${pathMappingItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/pathmap/details/4/${f:u(data.id)}">
                                                    <td>${f:h(data.regex)}</td>

        return this.fileId;
    }

    /**
     * Gets the decoded output data from the response.
     *
     * @return the outputData
     */
    public Decodable getOutputData() {
        return this.outputData;
    }

    /**
     * Gets the length of the output data.
     *
     * @return the outputLength
     */
    public int getOutputLength() {

                                                           items="${requestHeaderItems}">
                                                    <tr
                                                            data-href="${contextPath}/admin/reqheader/details/4/${f:u(data.id)}">
                                                        <td>${f:h(data.name)}</td>

  @Override
  protected Table<String, Integer, Character> create(@Nullable Object... data) {
    Table<String, Integer, String> table = HashBasedTable.create();
    checkArgument(data.length % 3 == 0);
    for (int i = 0; i < data.length; i += 3) {
      String value = (data[i + 2] == null) ? null : (data[i + 2] + "transformed");
      table.put((String) data[i], (Integer) data[i + 1], value);
    }
    return transformValues(table, FIRST_CHARACTER);
  }

(A SQL separator is semicolon ";")

take-finally-*.sql:
SQL statements for check loaded data (or DDL after data loading)
You should write your own SQL statements in this file.
(basically same specifications as replace-schema.sql)

The "data" directory is for data loading like this:
/- - - - - - - - - - - - - - - - - - - -
playsql
  |-data
     |-common
     |  |-xls
     |     |-10-master.xls
     |     |-defaultValueMap.dataprop

    var button = $(event.relatedTarget),
        docId = button.data("docid"),
        title = button.data("title"),
        url = button.data("url");

    $(this)
      .find(".modal-body #delete-doc-title")
      .text(title);
    $(this)
      .find(".modal-body #delete-doc-url")
      .text(url);
    $(this)
      .find(".modal-footer input#docId")
      .val(docId);
  });

								<group>root</group>
							</mapper>
						</data>
						<!-- Adds systemd file -->
						<data>
							<type>file</type>
							<src>${project.build.directory}/generated-packaging/deb/systemd/fess.service</src>
							<dst>${packaging.fess.systemd.dir}/fess.service</dst>
						</data>
						<!-- Adds systemd/sysctl.d configuration file -->
						<data>
							<type>file</type>