> 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/it/comandi-powershell/new-udeditor.md).

# New-UDEditor

New-UDEditor incorpora un editor di contenuti avanzato Editor.js in PowerShell Universal per creare contenuti di pagina strutturati e basati su blocchi.

### Sinossi

Crea un editor Editor.JS.

### Sintassi

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

### Descrizione

Crea un editor Editor.JS.

### Parametri

#### -Id

L'id dell'editor. Il valore predefinito è un nuovo GUID.

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

#### -Data

I dati da utilizzare per l'editor.

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

#### -OnChange

L'endpoint da chiamare quando l'editor cambia.

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

#### -Format

Il formato dei dati. Può essere json o html.

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

#### -PublishedFolder

Una cartella pubblicata in cui caricare i file. È richiesta per il plugin di caricamento immagini.

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

#### Parametri comuni

Questo cmdlet supporta i parametri comuni: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable e OutVariable. Per maggiori informazioni, veda [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Output

### Esempi

#### Esempio 1: editor di base

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

Un editor di base.

#### Esempio 2: editor HTML

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

Un editor che utilizza HTML.

#### Esempio 3: OnChange

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

Un editor con un blocco di script OnChange.

#### Esempio 4: HTML

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

Un editor che aggiorna un tag pre con il contenuto 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/powershell-universal/it/comandi-powershell/new-udeditor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.