[SERVER-80406] Add getSerializationContext function to OpMsgRequest Created: 24/Aug/23 Updated: 29/Oct/23 Resolved: 28/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sophia Tan | Assignee: | Sophia Tan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ntdi_must_have | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2023-09-04 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
The SerializationContext of command request comes from the body and validated tenant scope of OpMsgRequest. We need to add a function `getSerializationContext` to OpMsgRequest so that we can get serialization context more conveniently. |
| Comments |
| Comment by Githook User [ 26/Aug/23 ] |
|
Author: {'name': 'Sophia Tan', 'email': 'sophia_tll@hotmail.com', 'username': 'sophiatll'}Message: |