> 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/da/powershell-kommandoer/new-udeditor.md).

# New-UDEditor

New-UDEditor integrerer en Editor.js-editor til rigt indhold i PowerShell Universal til opbygning af struktureret, blokbaseret sideindhold.

### Synopsis

Opretter en Editor.JS-editor.

### Syntaks

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

### Beskrivelse

Opretter en Editor.JS-editor.

### Parametre

#### -Id

Id'et for editoren. Dette er som standard et nyt GUID.

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

#### -Data

De data, der skal bruges til editoren.

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

#### -OnChange

Det slutpunkt, der skal kaldes, når editoren ændres.

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

#### -Format

Formatet af dataene. Dette kan være json eller html.

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

#### -PublishedFolder

En publiceret mappe, som filer uploades til. Dette er påkrævet for billedupload-pluginet.

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

#### Fælles parametre

Denne cmdlet understøtter de fælles parametre: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable og OutVariable. Se [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216) for at få flere oplysninger.

### Output

### Eksempler

#### Eksempel 1: grundlæggende editor

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

En grundlæggende editor.

#### Eksempel 2: HTML-editor

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

En editor, der bruger HTML.

#### Eksempel 3: OnChange

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

En editor med en OnChange-scriptblok.

#### Eksempel 4: HTML

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

En editor, der opdaterer et pre-mærke med HTML-indholdet.


---

# 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/da/powershell-kommandoer/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.