[SERVER-60480] IDL fields which are ignored should not require a type Created: 05/Oct/21 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
The IDL allows for fields in a strict schema to be ignore: true, meaning that they can be safely omitted even when parsed in strict mode. Today these fields also require a type, even though that field has no semantic value since the field is never serialized / deserialized. We should remove type as a requirement when ignore: true is specified. |