Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **May** use stack view to display related key/value pairs. ``` There are valid use cases for key/value pairs without using a stack view.
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** use checkboxes in a tree view when more than one selection is allowed. ``` There is no support for multi-selection without checkboxes.
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** maintain consistency for checkboxes. **Must not** apply checkboxes to only some items in a tree view. ``` This is one line for icons and it's really the same thing sta...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** maintain consistency for checkboxes. **Must not** apply checkboxes to only some items in a tree view. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** use icons and checkboxes at the same time. It would result in large indentation and loss of space. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Should** use icons in order to visually represent the type of items in a tree. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** maintain consistency for icons. If icons need to be added to a tree view, apply the icons on all items. **Must not** to only some items in a tree view. ``` The website...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion ## Checkbox Tree ``` nit: missing blank line
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion ## Icon Tree ``` nit: missing blank line
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
I wonder if this one should be a "should not" instead because our documentation has an example with only one nested level.
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** use for only one level of nested information. Use an [accordion](https://clarity.design/documentation/accordion) instead. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** use too many levels unless it is for user-generated information. Instead, consolidate the layers if possible. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Phrase the label that clearly indicate the dropdown action. ``` No need for inline code styling here.
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Nested dropdown menus *should* be limited to three levels. ``` Let's use our keywords. :)
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** use dropdown menu as a form control. Use a [select](https://clarity.design/documentation/select) instead. ``` This one isn't optional. A dropdown *cannot* be used ...