Repository navigation
Conversation
…y sentence or fragment (CUI-73)
Hello cuervino,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
ℹ️ No review performedNo test review was performed: no code under test could be determined: the pull request changes no code and no tests. |
…te a text of several parts (CUI-73)
…lign examples (CUI-73)
| Exception: when displaying a list of resources (buckets, nodes, accounts…), each item may be capitalized as a proper noun if it represents a named entity. | ||
|
|
||
| This rule is enforced by the `technical-sentence-case` ESLint rule. | ||
| Do not use a full uppercase style. An uppercase label is harder to read than the same label in sentence case. An acronym keeps its capitals, such as S3, LDAP or URL. |
There was a problem hiding this comment.
Storybook itself breaks this new rule: the captions in stories/Toggle/toggle.stories.tsx:91, stories/guideline/responsive.stories.tsx:23 and stories/guideline/selection-controls-overview.stories.tsx:21 use textTransform: 'uppercase'. Drop the uppercase style there so the docs follow the rule they state.
Jira: CUI-73
Two gaps found while reviewing a dashboard page against the Style/Content guideline.