DOPE-253: add ANY AND EVERY #84
Conversation
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| typeExpression.predicate as (Iterator<ValidType>) -> TypeExpression<BooleanType> | ||
| val predicate = predicateFunc(Iterator(iteratorName)).toDopeQuery(manager) | ||
| CouchbaseDopeQuery( | ||
| queryString = "${typeExpression.satisfiesType} `$iteratorName` " + | ||
| queryString = "${typeExpression.satisfiesType.queryString} `$iteratorName` " + | ||
| "IN ${array.queryString} SATISFIES ${predicate.queryString} END", |
There was a problem hiding this comment.
TypeExpressionResolver now formats SatisfiesExpression with typeExpression.satisfiesType.queryString, but SatisfiesType exposes no queryString property or extension. This change fails to compile and prevents any query using ANY, EVERY, or the new ANY_AND_EVERY from being resolved at all. Either add a property mapping the enum values to their Couchbase keywords (e.g. “ANY AND EVERY”) or revert to using the enum name.
Useful? React with 👍 / 👎.
No description provided.