[YANGTOOLS-289] Failure to emit empty NETCONF-acquired data in JSON Created: 05/Sep/14 Updated: 10/Apr/22 Resolved: 05/Sep/14 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 1714 | ||||||||
| Description |
|
When we source data from NETCONF, the inbound codec emits an empty string for each empty element, overriding EmptyCodec's result (which is always null). This is incorrect behavior, which is manifested on egress in JSON writer, which ends up seeing a String instance where null is expected. Rather than adding a special case to the writer, fix ingress code structure to correctly assign value. |
| Comments |
| Comment by Robert Varga [ 05/Sep/14 ] |