> 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/apps/components/data-display/chip.md).

# Chip

Tilføj chipkomponenter til PowerShell Universal-apps med New-UDChip, der understøtter etiketter, ikoner, klikhændelser og slettehandlinger til kompakte brugerinteraktioner.

Chips er kompakte elementer, der repræsenterer et input, en attribut eller en handling.

Chips giver brugere mulighed for at indtaste oplysninger, foretage valg, filtrere indhold eller udløse handlinger.

Selvom den er medtaget her som en enkeltstående komponent, vil den mest almindelige anvendelse være i en form for input, så noget af den adfærd, der demonstreres her, ikke vises i sammenhæng.

## Grundlæggende chips

```powershell
 New-UDChip -Label 'Basic'
```

## Chips med ikoner

```powershell
New-UDChip -Label 'Basic' -Icon (New-UDIcon -Icon 'user')
```

## OnClick

Viser en toast, når der klikkes på chippen.

```powershell
New-UDChip -Label 'OnClick' -OnClick {
    Show-UDToast -Message 'Hello!'
}
```

## OnDelete

```powershell
New-UDChip -Label 'OnDelete' -OnClick {
    Show-UDToast -Message 'Goodbye!'
}
```

## **API**

[New-UDChip](/powershell-universal/da/powershell-kommandoer/new-udchip.md)


---

# 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/apps/components/data-display/chip.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.