fix: Return error instead of panicking when window rows/range is not a range#5603
Merged
fix: Return error instead of panicking when window rows/range is not a range#5603
Conversation
…a range Fixes PRQL#5601 When the `rows` or `range` parameter of `window` receives a non-range value (e.g., `rows:2` instead of `rows:0..2`), the compiler now returns a helpful error message instead of panicking. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
window rows:2was used instead of a range likerows:0..2.unwrap()calls to proper error handling with user-friendly error messagesparameter 'rows' expected a range, but found 2Test plan
rowsandrangeparameterstask test-alllocally - all tests pass🤖 Generated with Claude Code