Breadcrumb: v11 audit
See original GitHub issueAudit
A designer and developer will pair on this audit, some tasks may be discipline focused. Follow the checklist below for the features and items to review. If there are no issues with the item then check the item as complete. If any problems or bugs come up when auditing add a comment to this issue with the problem and how to correct it (if you know how). Bugs do not need to be fixed while auditing.
Resources
Checklist
Visual (in React code) Design and dev check
- Component is using the correct design tokens (color and type), see design spec and scss code.
- Component is rendering correctly across themes and layers, see design spec and storybook.
- White theme
- Gray 10 theme
- Gray 90 theme
- Gray 100 theme
- Component is rendering correctly across browsers (check themes across browsers as well), see storybook.
- Firefox
- Safari
- Chrome
- Component sizes are rendering and named correctly (if applicable)
Website (v11) Design checks
- Style tab has correct design tokens listed
- Style and usage tabs are using the correct size props names (if applicable)
- Usage tab is up-to-date for with any v11 behavioral changes (if any)
- Live Demo has applied v11 changes
- Themes are rendering correctly
- Size props are named correctly
- No
light
props included
Design Kits (Sketch only) Design checks
- Correct design tokens (type and color) are used
- Component using the correct size prop names
- Any additional v11 behaviors have been added
Storybook Dev checks
- Confirm that prop table is populating
- Take note of missing examples/stories (if any)
React package Dev checks
- Go to https://codesandbox.io/s/github/carbon-design-system/carbon/tree/main/packages/react/examples/codesandbox and confirm that you can use the component as expected from
@carbon/react
Accessibility Dev checks
- Confirm that there are no violations in Accessibility checker
- Confirm that component works as expected with VoiceOver
Migration docs Design and dev check
- Any breaking changes to this component are present in the v11 migration guide.
- Design
- Develop
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Group Audit Interface - Netwrix Documentation
The Group Audit interface is opened using the Search Features , conducting a search for a particular group. It contains the three panes...
Read more >BreadCrumb® ES1 Version 11 User Guide - FCC Report
It is possible to have a mesh with both v10 and v11 BreadCrumbs. ... In the event such audit discloses non-compliance with.
Read more >Working With Breadcrumbs - Rocket Software Documentation
When using breadcrumbs in Mobius View, the previous set of results is displayed, and the folder that was previously visited is shown in...
Read more >Follow the Audit Trail Breadcrumbs
Audit Trail Reviews Crucial for Maintaining Data Integrity. Data integrity is a hot topic for the U.S. FDA and other global regulatory ...
Read more >Migration from Verint v11 and v15.1 Legacy systems
The purpose of the migration is to import the historical recordings from the Verint v11, v15.1 Legacy systems to the Verba platform.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@thyhmdo in that code sample, if you look at the first line we set a local variable called
caret-size
, and just reference it in the block. It’s not a token that will appear anywhere else. Hope that clears that up 👍🏻Going to take a look at the rest of the dev audits now
Looks like this component is complete. Going to close this issue. @thyhmdo let me know if anything else needs to be done that I don’t see and we will re-open.
Live demo updates will be dealt with later. See https://github.com/carbon-design-system/carbon/issues/10889