-
-
Notifications
You must be signed in to change notification settings - Fork 446
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
Make Attachment immutable #1120
Comments
@bruno-garcia, @marandaneto, @maciejwalkowiak any objections to this change? |
no objections, just out of curiosity, what was the motivation to be a setter before? if none, even better :D |
I think I thought having to pass 3 parameters to a constructor is maybe a bit too much and we were not really sure back then if we even need content type. I think 3 parameters are fine. I can't remember what drove me back then. |
Removed the setter for contentType and added two new constructors. Now Attachment is immutable. Fixes GH-1120
Removed the setter for contentType and added two new constructors. Now Attachment is immutable. Fixes GH-1120
Removed the setter for contentType and added two new constructors. Now Attachment is immutable. Fixes GH-1120
Attachment has a setter for contentType. We can remove the setter and pass the param to the constructors instead. This means we need to add two constructors:
With this, we achieve immutability for Attachments.
The text was updated successfully, but these errors were encountered: