[SERVER-32177] IDL should generate a parse() overload that doesn't take an IDLParserErrorContext Created: 05/Dec/17 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | IDL, Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | 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 |
|
We are inconsistent with how we generate the IDLParserErrorContext when parsing top-level objects. IDL should handle constructing it "correctly" for top-level parsers (whatever we decide that means) and use it for nested parsing. |