- 
                Notifications
    You must be signed in to change notification settings 
- Fork 154
feat(user-avatar): add code connect config #8435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(user-avatar): add code connect config #8435
Conversation
| ✅ Deploy Preview for ibm-products-web-components ready!
 To edit notification comments on pull requests, go to your Netlify project configuration. | 
| ✅ Deploy Preview for carbon-for-ibm-products ready!
 To edit notification comments on pull requests, go to your Netlify project configuration. | 
| Codecov Report❌ Patch coverage is  Additional details and impacted files@@            Coverage Diff             @@
##             main    #8435      +/-   ##
==========================================
+ Coverage   79.38%   84.72%   +5.34%     
==========================================
  Files         474      375      -99     
  Lines       20340    17517    -2823     
  Branches     5006     4079     -927     
==========================================
- Hits        16146    14842    -1304     
+ Misses       4194     2675    -1519     
 🚀 New features to boost your workflow:
 | 
| Confirmed with @RichKummer, the web component example usage is showing as expected | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified in Code Connect and the generated code looks good to me.
2cbc991
    
Closes #8388
Adds the web component code connect config.
What did you change?
packages/ibm-products-web-components/package.jsonpackages/ibm-products-web-components/src/components/user-avatar/user-avatar.figma.tspackages/ibm-products-web-components/src/typings/resources.d.tsyarn.lockHow did you test and verify your work?
Wasn't able to verify, @RichKummer or @jlongshore might need you to double check me
PR Checklist
As the author of this PR, before marking ready for review, confirm you:
Updated documentation and storybook examplesWrote passing tests that cover this changeAddressed any impact on accessibility (a11y)Tested for cross-browser consistencyMore details can be found in the pull request section of
our contributing docs.