<img src="/img/tutorial/generate-clients/image02.png">

Sie erhalten außerdem automatische Vervollständigung für die zu sendende Payload:

<img src="/img/tutorial/generate-clients/image03.png">

/// tip | Tipp

Au même moment que durant l'exemple précédent, vous essayez de déclencher l'auto-complétion et vous voyez :

<img src="/img/python-types/image02.png">

Vous pouvez donc dérouler les options jusqu'à trouver la méthode à laquelle vous pensiez.

<img src="/img/python-types/image03.png">

## Plus de motivations

Cette fonction possède déjà des annotations de type :

    return result;
  }

  private String contentType(String path) {
    if (path.endsWith(".png")) return "image/png";
    if (path.endsWith(".jpg")) return "image/jpeg";
    if (path.endsWith(".jpeg")) return "image/jpeg";
    if (path.endsWith(".gif")) return "image/gif";
    if (path.endsWith(".html")) return "text/html; charset=utf-8";
    if (path.endsWith(".txt")) return "text/plain; charset=utf-8";

  /**
   * <a href="https://www.iana.org/assignments/media-types/image/heif">HEIF image format</a>.
   *
   * @since 28.1
   */
  public static final MediaType HEIF = createConstant(IMAGE_TYPE, "heif");

  /**
   * <a href="https://tools.ietf.org/html/rfc3745">JP2K image format</a>.
   *
   * @since 28.1
   */
  public static final MediaType JP2K = createConstant(IMAGE_TYPE, "jp2");

  /* audio types */

.brand-image-xl.single {\n  margin-top: -.3rem;\n}\n\n.brand-link.text-sm .brand-image,\n.text-sm .brand-link .brand-image {\n  height: 29px;\n  margin-bottom: -.25rem;\n  margin-left: .95rem;\n  margin-top: -.25rem;\n}\n\n.brand-link.text-sm .brand-image-xs,\n.text-sm .brand-link .brand-image-xs {\n  margin-top: -.2rem;\n  max-height: 29px;\n}\n\n.brand-link.text-sm .brand-image-xl,\n.text-sm .brand-link .brand-image-xl {\n  margin-top: -.225rem;\n  max-height: 38px;\n}\n\n.main-sidebar {\n  height: 100vh;\n...

drawing/x-dwf                  dwf              # AutoCAD
image/gif                      gif              # GIF image file
image/ief                      ief              # Image Exchange
image/jpeg                     jpeg jpg jpe     # JPG image file
image/png                      png              # Portable Network Graphics
image/tiff                     tiff tif         # TIFF image file
image/x-cmu-raster             ras              #

 *     public Collection<Lifecycle> provides() {
 *         return Collections.singleton(
 *             lifecycle("deploy-docker", Arrays.asList(
 *                 "build-image",
 *                 "tag-image",
 *                 "push-image"
 *             ))
 *         );
 *     }
 * }
 * </pre>
 *
 * @see org.apache.maven.api.Lifecycle
 * @see org.apache.maven.api.spi.ExtensibleEnumProvider
 * @since 4.0.0

- Build/lib/release: Explicitly use '--platform' in building server images
  
  When we switched to go-runner for building the apiserver,
  controller-manager, and scheduler server components, we no longer
  reference the individual architectures in the image names, specifically
  in the 'FROM' directive of the server image Dockerfiles.
  
  As a result, server images for non-amd64 images copy in the go-runner

errors.design_jsp_file_does_not_exist = El archivo JSP no existe.
errors.design_file_name_is_not_found = No se ha especificado el nombre del archivo.
errors.failed_to_write_design_image_file = No se pudo cargar el archivo de imagen.
errors.failed_to_update_jsp_file = No se pudo actualizar el archivo JSP.
errors.design_file_name_is_invalid = El nombre del archivo no es válido.
errors.design_file_is_unsupported_type = Este tipo de archivo no es compatible.

labels.facet_filetype_mp4a=MP4A Audio
labels.facet_filetype_oga=OGA Audio
labels.facet_filetype_wepb=WEBP Image
labels.facet_filetype_bmp=BMP Image
labels.facet_filetype_ico=ICO Image
labels.facet_filetype_png=PNG Image
labels.facet_filetype_svg=SVG Image
labels.facet_filetype_tiff=TIFF Image
labels.facet_filetype_jpg=JPEG Image
labels.facet_filetype_archive=Archive
labels.facet_filetype_bat=Batch File
labels.facet_filetype_c=C