This repository was archived by the owner on Dec 5, 2020. It is now read-only.
Support for advanced cq syntax #28
Open
Conversation
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
support for cq advanced syntax
ghost
added
the
|
can someone merge this? |
|
Any chance this can get merged sometime soon? This is pretty important functionality for working with continuous queries, and it would be more convenient to not have make my own custom fork of this provider just to get this functionality. |
|
This has been supplanted by #30, which has been merged. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
there is a bug in current provider which rejects cq's which has a advanced syntax and always expects a cq to start with select clause.
this PR fixes that and keeps backwards compatibility in place