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

fix: Token was not being resolved correctly #525

Merged
merged 1 commit into from
Nov 26, 2024
Merged

Conversation

tilucasoli
Copy link
Collaborator

Description

Token was not resolving correctly when the styled widget had inherited set to true, because the _tokenResolver was not being merged properly.

Changes

  • The MixData.merge method was modified;
  • Implemented a test specifically to handle this test.

Review Checklist

  • Testing: Have you tested your changes, including unit tests and integration tests for affected code?
  • Breaking Changes: Does this change introduce breaking changes affecting existing code or users?
  • Documentation Updates: Are all relevant documentation files (e.g. README, API docs) updated to reflect the changes in this PR?
  • Website Updates: Is the website containing the updates you make on documentation?

Copy link

vercel bot commented Nov 23, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
mix-docs ⬜️ Ignored (Inspect) Nov 23, 2024 3:50am

@github-actions github-actions bot added the mix label Nov 23, 2024
@tilucasoli tilucasoli merged commit 0f6542d into main Nov 26, 2024
6 checks passed
@tilucasoli tilucasoli deleted the fix/token-resolve branch November 26, 2024 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant