[SERVER-11143] Use Constraints in Option Parsing Created: 11/Oct/13 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Shaun Verch | Assignee: | Backlog - Security Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Server Security
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
The "Constraint" class represents a constraint on an option. It isn't being used heavily now, but eventually all our option validation should be done through constraints. This will make the description of our options completely declarative which will make it easier to verify and document. |
| Comments |
| Comment by Githook User [ 06/Dec/13 ] |
|
Author: {u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}Message: SERVER-11143 Added support for specifying that a string option must be of a specified format |
| Comment by Githook User [ 18/Nov/13 ] |
|
Author: {u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}Message: SERVER-11143 Add constraints for dependencies between options |
| Comment by auto [ 04/Nov/13 ] |
|
Author: {u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}Message: SERVER-11143 Add constraints to option registration interface |