> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/fr/commandes-powershell/new-udeditor.md).

# New-UDEditor

New-UDEditor intègre un éditeur de contenu enrichi Editor.js dans PowerShell Universal pour créer du contenu de page structuré basé sur des blocs.

### Synopsis

Crée un éditeur Editor.JS.

### Syntaxe

```powershell
New-UDEditor [[-Id] <String>] [[-Data] <Hashtable>] [[-OnChange] <Endpoint>] [[-Format] <String>] [[-PublishedFolder] <String>] [<CommonParameters>]
```

### Description

Crée un éditeur Editor.JS.

### Paramètres

#### -Id

L'id de l'éditeur. La valeur par défaut est un nouveau GUID.

```
Required?                    false
Position?                    1
Default value                ([Guid]::NewGuid())
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Data

Les données à utiliser pour l'éditeur.

```
Required?                    false
Position?                    2
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -OnChange

Le terminal à appeler lorsque l'éditeur change.

```
Required?                    false
Position?                    3
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Format

Le format des données. Il peut s'agir de json ou html.

```
Required?                    false
Position?                    4
Default value                json
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -PublishedFolder

Un dossier publié vers lequel téléverser des fichiers. Ceci est requis pour le module d'extension de téléversement d'images.

```
Required?                    false
Position?                    5
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### Paramètres communs

Cette applet de commande prend en charge les paramètres communs : Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable et OutVariable. Pour plus d'informations, voir [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Sorties

### Exemples

#### Exemple 1 : Éditeur de base

```powershell
New-UDEditor -Id 'editor1'
```

Un éditeur de base.

#### Exemple 2 : Éditeur HTML

```powershell
New-UDEditor -Id 'editor2' -Format 'html'
```

Un éditeur qui utilise HTML.

#### Exemple 3 : OnChange

```powershell
New-UDEditor -Id 'editor3' -OnChange {
    Show-UDToast $Body
}
```

Un éditeur avec un bloc de script OnChange.

#### Exemple 4 : HTML

```powershell
New-UDEditor -Format html -OnChange {
    Set-UDElement -Id 'test' -Content {
        $body
    }
}
New-UDElement -Tag pre -Id 'test'
```

Un éditeur qui met à jour une balise pre avec le contenu HTML.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devolutions.net/powershell-universal/fr/commandes-powershell/new-udeditor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.