Skip to content
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

[Components] @carbon/ibmdotcom-web-components Development v2 Epic #10715

Open
70 of 74 tasks
oliviaflory opened this issue Jul 19, 2023 · 0 comments
Open
70 of 74 tasks

[Components] @carbon/ibmdotcom-web-components Development v2 Epic #10715

oliviaflory opened this issue Jul 19, 2023 · 0 comments

Comments

@oliviaflory
Copy link
Contributor

oliviaflory commented Jul 19, 2023

Epic to track all component work for V2

Note

all work should be done in the feat/carbon-for-ibm-dotcom-v2 branch

This epic tracks the work to update all components in @carbon/ibmdotcom-web-components. Component styles and markup need to be updated as all upstream Carbon dependencies now use Carbon v11. As components in @carbon/web-components - an upstream dependency - have been upgraded to v11, the markup in many components in this package must be updated as well.

Issues with the v2 design change label have specific design requirements and may also introduce breaking changes. These issues should include updated design specs, component API changes, and may require working with the design team during implementation.

Component dependency map (Box Canvas)

Acceptance criteria

For all components, some basic acceptance criteria should be observed when working on them:

  • also update React wrapper
  • update Storybook docs
  • use visual design checklist before opening a PR (with emphasis on numbers 1, 2, and 6)
  • update migration guide if necessary (here is a good example of how the guide could look)
  • update unit tests where necessary (tracked in [Components]: Update @carbon/ibmdotcom-web-components v2 unit tests Epic #10369)
    • Note: Currently there is no standardization of tests, duplicate and/or redundant tests, and inconsistency in UI testing. The team consensus is to modify the tests as necessary (markup/name changes, etc) but to give this lower priority if it becomes a blocker in completing a particular component. The tests will get an overhaul in the future, so it is unnecessary to get them completely updated.

Components

Preview Give feedback
  1. package: web components v2
    emyarod
  2. package: web components v2
    annawen1
  3. package: web components v2
    ariellalgilmore
  4. dev package: web components v2
    ariellalgilmore
  5. bug dev package: web components severity 4
    sangeethababu9223
  6. dev package: web components v2 v2 design change
    ariellalgilmore
  7. dev v2 v2 NEW feature
    ariellalgilmore
  8. dev package: web components v2
    IgnacioBecerra kennylam
  9. dev package: web components v2 v2 design change
    ariellalgilmore
  10. dev v2 v2 design change
    ariellalgilmore oliviaflory
  11. package: web components v2
    IgnacioBecerra
  12. dev v2 v2 breaking change v2 design change
    annawen1
  13. dev v2 v2 design change
    annawen1
  14. dev v2 v2 design change
    RichKummer ariellalgilmore
  15. dev v2
    emyarod
  16. dev package: web components v2
    emyarod
  17. package: web components v2
    emyarod
  18. dev hacktoberfest v2
    annawen1
  19. dev package: web components v2
    kennylam
  20. dev v2
    sangeethababu9223
  21. dev hacktoberfest v2 v2 breaking change
    annawen1
  22. dev package: web components v2
    ariellalgilmore kennylam
  23. v2 v2 breaking change
    ariellalgilmore
  24. 0 of 3
    package: web components v2
    IgnacioBecerra
  25. dev package: web components v2
    IgnacioBecerra
  26. dev v2 v2 breaking change
    IgnacioBecerra
  27. dev v2
    IgnacioBecerra
  28. dev package: web components v2
    kennylam
  29. dev v2
    ariellalgilmore
  30. dev package: web components v2
    ariellalgilmore
  31. dev package: web components v2
    annawen1
  32. dev package: web components v2
    ariellalgilmore
  33. dev package: web components v2
    ariellalgilmore
  34. dev package: web components v2
    IgnacioBecerra
  35. dev package: web components v2 v2 design change
    ariellalgilmore
  36. v2 v2 design change
    IgnacioBecerra
  37. dev v2 v2 design change
    IgnacioBecerra
  38. dev package: web components v2
    sangeethababu9223
  39. dev v2
    kennylam
  40. package: web components v2 v2 breaking change v2 design change
    kennylam
  41. dev package: web components v2
    kennylam
  42. dev hacktoberfest package: web components v2
    annawen1
  43. dev package: web components v2
    annawen1
  44. dev package: web components v2
    ariellalgilmore
  45. dev package: web components v2
    ariellalgilmore
  46. v2 v2 design change
    annawen1
  47. dev package: web components v2
  48. dev package: web components v2
    ariellalgilmore
  49. dev package: web components v2 v2 design change
    ariellalgilmore
  50. 5 of 5
    dev v2 v2 breaking change
    emyarod
  51. dev package: web components v2
    ariellalgilmore
  52. dev package: web components v2
    ariellalgilmore
  53. dev v2 v2 breaking change
    emyarod
  54. dev package: web components v2
    kennylam
  55. dev package: web components priority: low v2
  56. dev package: web components v2
    ariellalgilmore

Deprecated Components

Preview Give feedback
  1. ariellalgilmore
@oliviaflory oliviaflory converted this from a draft issue Jul 19, 2023
@oliviaflory oliviaflory changed the title [Components] v2 Epic [Components] Development v2 Epic Jul 20, 2023
@kennylam kennylam changed the title [Components] Development v2 Epic [Components] @carbon/ibmdotcom-web-components Development v2 Epic Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Epics
Development

No branches or pull requests

1 participant