Skip to content

Conversation

@jbalboni
Copy link
Contributor

@jbalboni jbalboni commented Sep 22, 2025

Which problem is this PR solving?

Short description of the changes

This updates the granularity validation logic to match the API, where we allow granularities that create as few as 1 bucket in the query results, instead of 10.

How to verify that this has the expected result

Tests pass, I think.

@jbalboni jbalboni changed the title fix(query): Allow wider granularity range fix(r/query_specification): Allow wider granularity range Sep 22, 2025
@jbalboni jbalboni marked this pull request as ready for review September 22, 2025 20:46
@jbalboni jbalboni requested a review from a team as a code owner September 22, 2025 20:46
Copy link
Contributor

@jharley jharley left a comment

Choose a reason for hiding this comment

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

Looks good! Two quick things ahead of approval:

  1. the docs need to be updated as well as they're not autogenerated. docs/data-sources/query_specification.md (link)
  2. (minor) the PR title should be fix(d/query_specification): [...] as it's a data source not a resource

@jharley jharley added the bug label Sep 22, 2025
@jbalboni jbalboni changed the title fix(r/query_specification): Allow wider granularity range fix(d/query_specification): Allow wider granularity range Sep 22, 2025
@jbalboni jbalboni requested a review from jharley September 22, 2025 21:11
Copy link
Contributor

@jharley jharley left a comment

Choose a reason for hiding this comment

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

@jbalboni jbalboni merged commit d66b459 into main Sep 23, 2025
7 checks passed
@jbalboni jbalboni deleted the jbalboni.granularity-adjust branch September 23, 2025 12:42
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.

3 participants