-
Notifications
You must be signed in to change notification settings - Fork 52
MLE-23744 implement optic fromDocs in node client #1049
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
base: develop
Are you sure you want to change the base?
Conversation
|
Copyright Validation Results ✅ Valid Files
✅ All files have valid copyright headers! |
103b445 to
e0da9e3
Compare
a671f30 to
f3f1984
Compare
Add tweaked auto-generated functions and classes for optic fromDocs plan builder. Modify PlanColumnBuilder by adding PlanColumnBuilderBase to allow chaining during column definitions. This follows the patch builder pattern. Move transitiveClosure function after annTopK to match auto-generated code and make diff easier.
f3f1984 to
7cdc2ce
Compare
|
One pattern breaker: I added "types.Node" as a new additional param type for the vector() function. This matches other functions like op.xs.decimal in that they can accept an xpath result node. This supports an optic pattern like this that seems vital for the node client within fromDocs: |
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.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
Add tweaked auto-generated functions and classes for optic fromDocs plan builder. Modify PlanColumnBuilder by adding PlanColumnBuilderBase to allow chaining during column definitions. This follows the patch builder pattern. Move transitiveClosure function after annTopK to match auto-generated code and make diff easier.