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: get response count in analysis layout more efficiently #1875

Merged
merged 2 commits into from
Jan 10, 2024

Conversation

mattinannt
Copy link
Member

What does this PR do?

fix: get response count in analysis layout more efficiently

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (refactoring code, technical debt, workflow improvements)
  • Enhancement (small improvements)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change adds a new database migration
  • This change requires a documentation update

Copy link

vercel bot commented Jan 10, 2024

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

2 Ignored Deployments
Name Status Preview Comments Updated (UTC)
formbricks-cloud ⬜️ Ignored (Inspect) Visit Preview Jan 10, 2024 9:35am
formbricks-com ⬜️ Ignored (Inspect) Jan 10, 2024 9:35am

Copy link
Contributor

github-actions bot commented Jan 10, 2024

Thank you for following the naming conventions for pull request titles! 🙏

@mattinannt mattinannt changed the title get response count in analysis layout more efficiently fix: get response count in analysis layout more efficiently Jan 10, 2024
@mattinannt mattinannt added this pull request to the merge queue Jan 10, 2024
Merged via the queue into main with commit a0d7921 Jan 10, 2024
12 of 13 checks passed
@mattinannt mattinannt deleted the feature/update-layout branch January 10, 2024 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant