-
Notifications
You must be signed in to change notification settings - Fork 102
[Proposal] Transform script into a container #2708
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
Conversation
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
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.
If we're going that route, I would go as far as not making it a container: lang
and options
only apply to inline script, so it's weird to allow id
xor source
while having these container properties that will cause a server-side failure if set for the wrong variant.
I like the container solution a little bit better over the single interface, but no strong preference here. Fine with a single interface as well. This is definitely better than what we currently have. |
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
RoleTemplateInlineScript has duplicate fields from ScriptBase, we should remove lang and options |
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
LGTM but it breaks deserialization for RoleTemplateScript the java client, if we could wait until I fix it before merging this |
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.
LGTM.
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.15 8.15
# Navigate to the new working tree
cd .worktrees/backport-8.15
# Create a new branch
git switch --create backport-2708-to-8.15
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 90fe7e26253312b8efb4cad3fcb5c49e02bb325d
# Push it to GitHub
git push --set-upstream origin backport-2708-to-8.15
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.15 Then, create a pull request where the |
* transform script union to a container variant * Remove unused imports * refresh outputs * remove wrongly added empty files * merge script into a standard class * add output * remove duplicated fields * add newly generated output * simplify RoleTemplateScript to reflect Script changes * add newly generated output * make source option in RoleTemplateScript (cherry picked from commit 90fe7e2)
* transform script union to a container variant * Remove unused imports * refresh outputs * remove wrongly added empty files * merge script into a standard class * add output * remove duplicated fields * add newly generated output * simplify RoleTemplateScript to reflect Script changes * add newly generated output * make source option in RoleTemplateScript (cherry picked from commit 90fe7e2)
@shortcut_property
onInlineScript
is unreachable from the union.From the server code,
Script
could benefit from being a container instead.