-
Notifications
You must be signed in to change notification settings - Fork 361
fix: Change None aggregation to Custom #1633
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
Conversation
For clarity
🦋 Changeset detectedLatest commit: f458f3d The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
✅ No critical issues found. This is a straightforward UX improvement that makes the aggregation label more intuitive for users. The change is well-scoped and includes an appropriate changeset. |
E2E Test Results✅ All tests passed • 61 passed • 4 skipped • 766s
Tests ran across 4 shards in parallel. |
Justification: "None" is confusing to customers. Custom reflects the ability for users to use their own aggregation in the where clause.