[SERVER-29622] IDL's generated class constructors should respect a parameter's specified default value Created: 14/Jun/17  Updated: 29/Jan/18  Resolved: 30/Jun/17

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: 3.5.8
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Mark Benvenuto
Resolution: Duplicate Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-29743 IDL should generate a default constru... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platforms 2017-07-10
Participants:

 Description   

Marked component as Networking because I'm not sure what it should be - feel free to change.



 Comments   
Comment by Esha Maharishi (Inactive) [ 14/Jun/17 ]

To get around this in the meantime, any time I build an IDL type using its default constructor, I'm explicitly setting the fields that should use the default value with the corresponding set() method, and putting a comment with this ticket number above them.

This is relevant for the "Move all metadata commands to the config server" (PM-696) project, where the command request to the config server is built on mongos using the default constructor.

Generated at Thu Feb 08 04:21:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.