-
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
GODRIVER-2962 Remove setters from Aggregate. #1372
GODRIVER-2962 Remove setters from Aggregate. #1372
Conversation
API Change Report./x/mongo/driver/operationincompatible changes(*Aggregate).AllowDiskUse: removed compatible changesAggregate.AllowDiskUse: added |
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!
The base branch was changed.
36e139c
to
f5ee31a
Compare
Is this meant to be part of the 2.0 epic then? |
@blink1073 no, this is not a strictly v2 change. I switched the branch to minimize the additional work required to sync changes from |
Should we mark the setters as deprecated in v1? |
@blink1073 Yes. Considering the feedback we've received about the unannounced removal of some other experimental APIs, I think marking those as deprecated in v1.x would be useful messaging. |
Closing this for now, will follow up later when GODRIVER-2962 is scheduled. |
GODRIVER-2962
Summary
Remove setters from
Aggregate
.Background & Motivation
The field setters on the operation types in the
x/mongo/driver/operation
package provide no usability improvement but create a maintenance burden whenever we have to update the operations. Remove the field setters and use struct literals instead.Split the change into multiple PRs to make reviewing them easier.