[Draft] Token management pipeline testing #1498
Draft
Conversation
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
Accessibility Test results
Details
|
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Playwright test results
Details
Skipped testssrc/components/table/table/test/expandable-row-autocollapse/expandable-row-autocollapse.e2e.ts › tds-table-expandable-row-autoCollapse › NEEDS FIXING: expanding one row collapses the others when autoCollapse is true |
timrombergjakobsson
force-pushed
the
feat/token-management
branch
from
384d2f1 to
84ecd48
Compare
No manual adjustments in this commit, just a clean import from Figma to Tokens Studio plugin from the main branch
For easier filtering and exclusion. Includes a new bucket for stuff related to `__content` which we also do not need in the tokens structure right now
timrombergjakobsson
force-pushed
the
feat/token-management
branch
from
84ecd48 to
c632410
Compare
|
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.
Describe pull-request
Just a draft PR for now, to see what kind of merge conflicts and/or changes the current variables structure would present when compared to
develop.Issue Linking:
How to test
[TBA]
Checklists, test steps, screenshots & additional context
## **Checklist before submission** - [ ] Designer approves new design (if applicable) - [ ] No accessibility violations in Storybook - [ ] I have added unit tests for my changes (if applicable) - [ ] All existing tests pass - [ ] I have updated the documentation (if applicable) - [ ] Not breaking production behavior - [ ] Behavior available in Storybook with documented descriptions (if applicable) - [ ] `npm run build:all` without errors
Suggested test steps
Screenshots
Include before/after screenshots for UI changes.
Additional context
Add any other context or feedback requests about the pull-request here.