feat: update troubleshooting filters and navigation#1243
Merged
Conversation
✅ Deploy Preview for elated-hoover-5c29bf ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
A total of 32 tests failed! API guides documentation page1 failing tests:
API reference documentation page1 failing tests:
Status of documentation pages30 failing tests:
For more information, open the cypress action summary page. |
carolinamenezes
requested changes
May 20, 2026
Contributor
carolinamenezes
left a comment
There was a problem hiding this comment.
Rodar o prettier para evitar erros no deploy
Fix formatting to resolve deploy lint/prettier checks. Co-authored-by: Cursor <cursoragent@cursor.com>
Performance ResultsPage /docs/api-reference/catalog-api-seller-portal#get-/api/catalog-seller-portal/products/-productId-Complete results here Page /docs/troubleshooting/google-analytics-4-is-tracking-inconsistent-data-from-my-storeComplete results here Page /updates/release-notes/2025-08-29-orders-api-support-for-nt-2025-001-fieldsComplete results here Overall Performance |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of this pull request?
Summary
This PR updates the Troubleshooting experience in
devportalto support the new troubleshooting taxonomy fromdev-portal-content.What changed
domainFilterssymptomFilterstagsfallback for compatibility where neededTypeAreadocs/troubleshootingpublic/navigation.jsonTroubleshooting categories to the new structure:API and integrationsVTEX IO and app developmentStorefrontContent Management (CMS)Checkout and shopping experienceAnalytics and data collectionDependency
This PR depends on the corresponding
dev-portal-contentbranch:EDU-17951-Enable-tagging-system-for-Troubleshooting-(Developer-Portal)That branch already includes the final strategy alignment, so this UI implementation is based on the finalized taxonomy.
Notes
RapiDocwas intentionally not includedValidation
public/navigation.jsonnodeandcypressWhat problem is this solving?
How should this be manually tested?
Screenshots or example usage
Types of changes