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: use strategyName instead of name property for component to load #8983

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

daveleek
Copy link
Contributor

resolves which component to load based on strategyName instead of name, as the former is always present

Skjermbilde 2024-12-16 kl  08 38 49

after switch

Skjermbilde 2024-12-16 kl  08 39 11

Copy link

vercel bot commented Dec 16, 2024

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

Name Status Preview Comments Updated (UTC)
unleash-monorepo-frontend ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 16, 2024 7:42am
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
unleash-docs ⬜️ Ignored (Inspect) Dec 16, 2024 7:42am

Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Files

Copy link
Contributor

@gastonfournier gastonfournier left a comment

Choose a reason for hiding this comment

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

LG

@daveleek daveleek merged commit 76dfa3c into main Dec 16, 2024
13 checks passed
@daveleek daveleek deleted the fix/ui-couldnt-resolve-strategy-name branch December 16, 2024 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants