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: max depth error in equal prominence #1617

Merged
merged 2 commits into from
Aug 14, 2023
Merged

fix: max depth error in equal prominence #1617

merged 2 commits into from
Aug 14, 2023

Conversation

raviteja83
Copy link
Collaborator

Details(context, Jira ticket, how was the bug fixed, what does the new feature do)

Choose one of these(put a 'x' in the bracket):

  • The change doesn't require a change to the documentation.
  • The documentation is updated accordingly.

Implementation note, gotchas, related work and Future TODOs (optional)

@vercel
Copy link

vercel bot commented Aug 14, 2023

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

Name Status Preview Comments Updated (UTC)
dashboard-app ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 14, 2023 0:01am
storybook-app ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 14, 2023 0:01am

@github-actions
Copy link
Contributor

A JIRA Issue ID is missing from your branch name! 🦄

Your branch: fix/max-depth

If this is your first time contributing to this repository - welcome!


Please refer to jira-lint to get started.

Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail.

Valid sample branch names:

‣ feature/shiny-new-feature--mojo-10'
‣ 'chore/changelogUpdate_mojo-123'
‣ 'bugfix/fix-some-strange-bug_GAL-2345'

@raviteja83 raviteja83 changed the title fix: max depth error fix: max depth error in equal prominence Aug 14, 2023
@raviteja83 raviteja83 requested a review from eswarclynn August 14, 2023 11:25
eswarclynn
eswarclynn previously approved these changes Aug 14, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Aug 14, 2023

size-limit report 📦

Path Size
packages/hms-video-web/dist/index.cjs.js 60.64 KB (0%)
packages/hms-video-web/dist/index.js 60.44 KB (0%)
packages/hms-video-store/dist/index.cjs.js 17.72 KB (0%)
packages/hms-video-store/dist/index.js 17.48 KB (0%)
packages/roomkit-react/dist/index.cjs.js 206.02 KB (+0.01% 🔺)
packages/roomkit-react/dist/index.js 560 B (-0.54% 🔽)
packages/hms-virtual-background/dist/index.cjs.js 5.12 KB (0%)
packages/hms-virtual-background/dist/index.js 4.91 KB (0%)
packages/hms-noise-suppression/dist/index.cjs.js 2.15 KB (0%)
packages/hms-noise-suppression/dist/index.js 1.87 KB (0%)

@github-actions
Copy link
Contributor

A JIRA Issue ID is missing from your branch name! 🦄

Your branch: fix/max-depth

If this is your first time contributing to this repository - welcome!


Please refer to jira-lint to get started.

Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail.

Valid sample branch names:

‣ feature/shiny-new-feature--mojo-10'
‣ 'chore/changelogUpdate_mojo-123'
‣ 'bugfix/fix-some-strange-bug_GAL-2345'

@raviteja83 raviteja83 merged commit fdc0737 into main Aug 14, 2023
@raviteja83 raviteja83 deleted the fix/max-depth branch August 14, 2023 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants