</c:set>
						<la:password property="oldPassword" class="form-control"
									 placeholder="${ph_old_password}" />
						<div class="input-group-append">
							<span class="input-group-text"><i class="fa fa-lock fa-fw" aria-hidden="true"></i></span>
						</div>
					</div>
					<div class="input-group mb-3">
						<c:set var="ph_new_password">
							<la:message key="labels.profile.placeholder_new_password" />
						</c:set>

## Resumen { #recap }

Usa el parámetro `response_model` del *decorador de path operation* para definir modelos de response y especialmente para asegurarte de que los datos privados sean filtrados.

                            <div class="card-body">
                                <div class="form-group row">
                                    <span class="font-weight-bold col-sm-3 text-sm-right col-form-label"><la:message
                                            key="labels.replace_aliases"/></span>
                                    <div class="form-inline col-sm-9">
                                        <la:errors property="replaceAliases"/>

                                                        aria-label="Close">
                                                    <span aria-hidden="true">×</span>
                                                </button>
                                            </div>
                                            <div class="modal-body">

						</c:set>
						<la:password property="password" class="form-control"
							placeholder="${ph_new_password}" />
						<div class="input-group-append">
							<span class="input-group-text">
								<i class="fa fa-lock fa-fw" aria-hidden="true"></i>
							</span>
						</div>
					</div>
					<div class="input-group mb-3">
						<c:set var="ph_confirm_password">

																	<span class="badge bg-primary"><la:message
                                                                            key="labels.enabled"/></span>
                                                    </c:if> <c:if test="${data.available=='false'}">
																	<span class="badge bg-gray"><la:message

                                </a>
                                <c:forEach var="item" varStatus="s" items="${pathItems}">
                                    / <span><a
                                        href="${contextPath}/admin/storage/list/${f:u(item.id)}/">${f:h(item.name)}</a></span>
                                </c:forEach>
                                / <c:if test="${editable}"><a data-toggle="modal" data-target="#createDir" href="#"><i

    /** Array of fields that can be highlighted in search results */
    protected String[] highlightedFields;

    /** Array of fields that can be searched against */
    protected String[] searchFields;

    /** Set of fields that can be searched against for O(1) lookup */
    protected Set<String> searchFieldSet;

    /** Array of fields that can be used for faceted search */
    protected String[] facetFields;

{* ../../docs_src/query_params_str_validations/tutorial006_an_py39.py hl[9] *}

### Required, can be `None` { #required-can-be-none }

You can declare that a parameter can accept `None`, but that it's still required. This would force clients to send a value, even if the value is `None`.

                                                                                aria-label="Close">
                                                                            <span aria-hidden="true">×</span>
                                                                        </button>
                                                                    </div>