-
Notifications
You must be signed in to change notification settings - Fork 891
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
Operator API #2503
Operator API #2503
Conversation
7bbf75b
to
b5b5ef0
Compare
d26349e
to
5a72a3b
Compare
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.
Most of the handler code is copied from AdminHandler
, right? And you gonna keep it there for some period of time. It would be great to reduce code duplication and have an instance of OpearatorHandler
in AdminHandeler
and call these 3 methods from it. With proper comment that it is deprecated and so on.
0e6bc34
to
730763e
Compare
@alexshtin I would generally agree with you about code duplication if there are two different active endpoints that are using the same code. The way you propose to directly use operator_handler in admin_handler will not fly, because operator_handler doesn't provide a superset of operations/return values, the endpoints are slightly different. For example, the new operator endpoint doesn't return some of the data that is returned by the deprecated version ( This way, every time we will be editing the new version of the code you will have to worry about not breaking and supporting the code paths used by the deprecated version. Compare it with the current approach, where we will be just directly editing the new endpoints and can forget about updating the old ones. |
e690b80
to
bd59d52
Compare
I would agree on this. Let's leave two copies. |
e491aef
to
642ffc9
Compare
642ffc9
to
39d758b
Compare
Operator Service with Search Attributes
39d758b
to
791b33f
Compare
No description provided.