/**
 * MS-RPC share information retrieval operation.
 *
 * This class implements the Server Service (SRVSVC) ShareGetInfo operation
 * for retrieving detailed information about a network share, including
 * security descriptors.
 */
public class MsrpcShareGetInfo extends srvsvc.ShareGetInfo {

    /**
     * Creates a new request to get share information.
     *
     * @param server the server name

///

You can add a `title`:

{* ../../docs_src/query_params_str_validations/tutorial007_an_py310.py hl[10] *}

And a `description`:

{* ../../docs_src/query_params_str_validations/tutorial008_an_py310.py hl[14] *}

## Alias parameters { #alias-parameters }

Imagine that you want the parameter to be `item-query`.

Like in:

    interface Transformer {
        /**
         * Interpolate the value read from the xml document
         *
         * @param source    The source value
         * @param fieldName A description of the field being interpolated. The implementation may use this to
         *                  log stuff.
         * @return the interpolated value
         */
        String transform(String source, String fieldName);

        val descriptionSuffix =
            if (descriptionParts.isNotEmpty()) {
                " (${descriptionParts.joinToString(separator = ", ")})"
            } else {
                ""
            }
        description =
            "Builds Gradle with the version of Gradle which is currently under development (twice)$descriptionSuffix"

        requirements {

As chaves do `dict` identificam cada exemplo, e cada valor é outro `dict`.

Cada `dict` de exemplo específico em `examples` pode conter:

* `summary`: Pequena descrição do exemplo.
* `description`: Uma descrição longa que pode conter texto em Markdown.
* `value`: O próprio exemplo mostrado, ex: um `dict`.

Poderia ser assim:

```JSON  hl_lines="7"
{
  "name": "frontend-app",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "generate-client": "openapi-ts --input http://localhost:8000/openapi.json --output ./src/client --client axios"
  },
  "author": "",
  "license": "",

ldap.attr.homePostalAddress=homePostalAddress
# LDAP attribute for labeled URI.
ldap.attr.labeledURI=labeledURI
# LDAP attribute for room number.
ldap.attr.roomNumber=roomNumber
# LDAP attribute for description.
ldap.attr.description=description
# LDAP attribute for title.
ldap.attr.title=title
# LDAP attribute for pager.
ldap.attr.pager=pager
# LDAP attribute for street.
ldap.attr.street=street

        // restore from pager
        copyBeanToBean(fileConfigPager, form, op -> op.include("name", "paths", "description"));
    }

    // ===================================================================================
    //                                                                        Edit Execute

Podría verse como esto:

```JSON  hl_lines="7"
{
  "name": "frontend-app",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "generate-client": "openapi-ts --input http://localhost:8000/openapi.json --output ./src/client --client axios"
  },
  "author": "",
  "license": "",

일부는 아직 선언된 추가 정보를 모두 표시하지 않을 수 있지만, 대부분의 경우 누락된 기능은 이미 개발 계획이 있습니다.

///

`title`을 추가할 수 있습니다:

{* ../../docs_src/query_params_str_validations/tutorial007.py hl[10] *}

그리고 `description`도 추가할 수 있습니다:

{* ../../docs_src/query_params_str_validations/tutorial008.py hl[13] *}

## 별칭 매개변수

매개변수가 `item-query`이길 원한다고 가정해 봅시다.

마치 다음과 같습니다:

```