通过代码从同一源创建了2个大的JSON(〜GB)文件，它们应该完全相同，但是有时应该会有一些细微的差异.
Have 2 big JSON (~GB) files created from same source by code, that should work exactly same, but there should be some small differences sometimes.
希望确保两次转换都能正确完成相同的工作.做了一个小项目，将JSON转换为CSV类型，并带有指向元素及其内容(单个值或数组/对象)的路径.然后计划通过任何文本差异来比较"CSV" JSON.
Want to be sure both conversions did same job and properly. Made small project to convert JSONs to kind of CSV with path to elements and its content (single value or arrays/objects). Planning to compare "CSV" JSONs by any text diff then.
来源(在我的GitHub上)相当长，有限制这里的空间并不是问题的主要部分.通常它不能正常工作(已在一个大型的简单JSON上进行了测试，并在此处显示了另一个示例，不想使用递归，代码非常棘手).
Source (on my GitHub) is quite long for limitted space here and is not main part of the question. It is not working properly generally (tested on a big simple JSON and another shown here, did not want to use recursion, code is quite tricky).
示例导出 JSON数据集示例#示例4 当ID设置为类型，水平格式和全部排序时，说明我的想法如下:
Example export of JSON Data Set Sample # Example 4 to ilustrate my idea when ID set to type, Horizontal format and Sort All looks like:
batters\batter\Blueberry\ id 1003 batters\batter\Devil's Food\ id 1004 batters\batter\Chocolate\ id 1002 batters\batter\Regular\ id 1001 donut\ id 0001 name Cake ppu 0.55 topping\Glazed\ id 5002 topping\Chocolate with Sprinkles\ id 5006 topping\Chocolate\ id 5003 topping\Maple\ id 5004 topping\None\ id 5001 topping\Powdered Sugar\ id 5007 topping\Sugar\ id 5005是个好主意还是有更好的选择?
已处理的JSON预览:
{ "type": "donut", "id": "0001", "name": "Cake", "ppu": 0.55, "batters": { "batter": [ { "id": "1001", "type": "Regular" },{ "id": "1002", "type": "Chocolate" },{ "id": "1003", "type": "Blueberry" },{ "id": "1004", "type": "Devil's Food" }]}, "topping": [ { "id": "5001", "type": "None" },{ "id": "5002", "type": "Glazed" },{ "id": "5005", "type": "Sugar" }, ...推荐答案
至少有2个选项-在另一个问题中的第一处，并且在我的GitHub上将新方法 RemoveTwins 添加到Gason C ++中并转换为C#.
Have at least 2 options yet - 1st here in another question and new method RemoveTwins added to Gason C++ translated to C# - on my GitHub.
更多推荐
如何比较大JSON?
发布评论