Skip to content

feat: add shared troubleshooting listing components#84

Open
ricardoaerobr wants to merge 2 commits into
mainfrom
feat/EDU-18208-troubleshooting-shared-components
Open

feat: add shared troubleshooting listing components#84
ricardoaerobr wants to merge 2 commits into
mainfrom
feat/EDU-18208-troubleshooting-shared-components

Conversation

@ricardoaerobr

@ricardoaerobr ricardoaerobr commented Jun 8, 2026

Copy link
Copy Markdown

Summary

  • Add shared Tag, ListingFilter, and TroubleshootingCard components
  • Add filterTroubleshootingItems and collectTroubleshootingFilterOptions utilities
  • Support Dev Portal and Help Center variants while keeping portal-specific data and routing

Implementation steps (required)

  1. Merge this PR first — portal PRs depend on these exports.
  2. Release @vtexdocs/components after merge (e.g. v6.0.39 if v6.0.35 already exists on remote).
  3. Share the new tag with Dev Portal and Help Center PR authors.
  4. Portal PRs must not be merged until this package is released and portals point to the new tag.

Portal follow-up (after release)

In devportal and helpcenter, update package.json:

"@vtexdocs/components": "https://github.com/vtexdocs/components.git#v6.0.xx"

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Requires change to documentation, which has been updated accordingly.

Extract Tag, ListingFilter, TroubleshootingCard, and troubleshooting filter utilities so Help Center and Dev Portal can share the same UI while keeping portal-specific content and routing.

Co-authored-by: Cursor <cursoragent@cursor.com>
…eshooting-shared-components

# Conflicts:
#	dist/index.css.map
#	dist/index.mjs
#	dist/index.mjs.map
#	package.json

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pull request does not contain a valid label. Please add one of the following labels: ['release-no', 'release-auto', 'release-patch', 'release-minor', 'release-major']

@ricardoaerobr ricardoaerobr added the release-no No release bump label Jun 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-no No release bump

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant