Content
View differences
Updated by Judith Roth 4 months ago
**As** a user being used to work packages and the way how work package types are visually "encoded" (uppercase)
**I want to** see document types being rendered, too
**so that** I don't have to learn a new pattern.
**Acceptance criteria**
* The rendering of work package types and document types in the dropdown are rendered in capital letters and bold (try to reuse existing styles if possible, e.g. the class `hl__inline__type`) very similar
**Technical notes**
* I know that the type selector for WPs is not primerized and that we cannot say when exactly that will be
* I believe that it is not so hard to add a uppercase style for the time being to the new documents type selector.
**Out of scope**
* Having only one component for type renderings that covers both work packages and documents.
* Changing the position of the dropdown
**I want to** see document types being rendered, too
**so that** I don't have to learn a new pattern.
**Acceptance criteria**
* The
**Technical notes**
* I know that the type selector for WPs is not primerized and that we cannot say when exactly that will be
* I believe that it is not so hard to add a uppercase style for the time being to the new documents type selector.
**Out of scope**
* Having only one component for type renderings that covers both work packages and documents.
* Changing the position of the dropdown