> For the complete documentation index, see [llms.txt](https://docs.yemreak.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yemreak.com/arsiv/programming/type-alias-gosterimi-sorunu-ve-cozumu.md).

# Type Alias Gösterimi Sorunu ve Çözümü

typescript, programming

## Type Alias Gösterimi Sorunu ve Çözümü

![DALLE\_2023-10-26\_23.53.04\_-\_illustration\_of\_a\_very\_cute\_cat\_with\_lineal\_colors\_lying\_down\_on\_a\_desk\_with\_programming\_books\_a\_cup\_with\_the\_TypeScript\_logo\_and\_type\_symbols.png](https://i.imgur.com/OVs1soM.jpg)

### İçerikte alttaki sorunlara çözüm bulacağız:

1. "VS Code TypeScript type hover display issue"
2. "VS Code displaying type alias as template literal TypeScript"
3. "Change how VS Code shows TypeScript type aliases"
4. "TypeScript type resolution problem in VS Code hover"
5. "VS Code not resolving TypeScript type alias correctly"

## TypeScript ile basit **`type`** yapıları tanımladığımızda yeni isim yerine detaylarını gösteriyor.

```typescript
export type PairId = Readonly<`${AssetSymbol}_${AssetSymbol}`>
```

![28z4XuP.png](https://i.imgur.com/28z4XuP.png)

## Sorunu çözmek için **`alias`** isimli ek bir **`type`** daha tanımlıyoruz.

```typescript
type alias<t> = t & { _?: never }
export type PairId = alias<Readonly<`${AssetSymbol}_${AssetSymbol}`>>
```

![hfOWuBF.png](https://i.imgur.com/hfOWuBF.png)

## Referanslar

{% embed url="<https://github.com/microsoft/TypeScript/issues/31940#issuecomment-1555533360>" %}


---

# 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.yemreak.com/arsiv/programming/type-alias-gosterimi-sorunu-ve-cozumu.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.