feat(sanity): support create live data with single query#8
Merged
Conversation
✅ Deploy Preview for limitless-angular-sanity-example ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
View your CI Pipeline Execution ↗ for commit c7d95d8.
☁️ Nx Cloud last updated this comment at |
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
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.
PR Checklist
This PR enhances the documentation and functionality of
createLiveDatain the Sanity package.What is the new behavior?
Added documentation for single query usage of
createLiveDataEnhanced
createLiveDatato support both single query and multiple queries configurationsAdded code examples demonstrating both usage patterns:
Updated type definitions to support both patterns
Enhanced parameter documentation to clarify the two supported query configurations
Does this PR introduce a breaking change?
Other information
This change improves developer experience by simplifying the API for single query use cases while maintaining backward compatibility for multiple queries.
[Optional] What gif best describes this PR or how it makes you feel?