[SERVER-83797] Introduce DatabaseNameUtil (de)serialize functions for non idl generated code Created: 01/Dec/23 Updated: 07/Feb/24 |
|
| Status: | In Code Review |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathis Bessa | Assignee: | Mathis Bessa |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ntdi_code_quality, ntdi_must_have | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Sprint: | Service Arch 2024-01-08, Service Arch 2024-01-22, Service Arch 2024-02-05, Service Arch 2024-02-19 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||||||
| Description |
|
We are currently transitioning to using a ValidatedTenancyScope as a source of truth in order to serialize / deserialize database names. As part of Because we are still serializing using a SerializationContext, we can not remove the SerializationContext as part of the constructor in the IDLParser In this ticket, we should create Serialization / Deserialization for DatabaseNameUtil that takes in a ValidatedTenancyScope. The behavior should be identical to the way the SerializationContext does.
|