-
Notifications
You must be signed in to change notification settings - Fork 2
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
chore: snowpipe streaming category not a warehouse #1778
base: develop
Are you sure you want to change the base?
Conversation
WalkthroughThe pull request modifies the Changes
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
🔇 Additional comments (1)src/schemas/destinations/db-config-schema.json (1)
The schema change correctly enables empty category support while maintaining backward compatibility for warehouse destinations. Let's verify if any validation logic depends on non-empty category values: ✅ Verification successfulLet's examine the validation test file to ensure there are no assumptions about non-empty categories. Let's check the validation implementation to see how category is handled. Let's try a broader search for validation-related files and category handling. Let's examine the validator implementation to ensure there are no category-specific validations. Schema change is safe to proceed The validation implementation uses standard JSON Schema validation through AJV without any custom logic for category values. The empty string in the enum is properly handled by the schema validator, and there are no additional constraints or assumptions about non-empty categories in the codebase. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Search for validation logic that might assume non-empty category
# Check for category-related validation patterns
rg -g '!*.{json,md}' -i 'category.*warehouse|warehouse.*category' .
# Look for potential validation files
fd -e ts -e js -e go validation
Length of output: 127 Script: #!/bin/bash
# Check validation test content for category-related tests
cat test/validation.test.ts
Length of output: 10083 Script: #!/bin/bash
# Check the validation implementation
fd -e ts -e js validate src/
Length of output: 30 Script: #!/bin/bash
# Search for validation-related files and category handling
rg -l "validateDestination|validateConfig" src/
rg -l "category.*validate|validate.*category" src/
Length of output: 125 Script: #!/bin/bash
# Check the validator implementation
cat src/validator/index.ts
Length of output: 3494 Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
src/configurations/destinations/snowpipe_streaming/db-config.json
Outdated
Show resolved
Hide resolved
ccac5d0
to
dc768db
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1778 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 2 2
Lines 53 53
Branches 7 7
=========================================
Hits 53 53 ☔ View full report in Codecov by Sentry. |
8fe5b74
to
3a9bea4
Compare
3a9bea4
to
968a960
Compare
What are the changes introduced in this PR?
What is the related Linear task?
Summary by CodeRabbit