channeliq / jsoncompare Goto Github PK

A simple python library for comparing json objects for equivalency and helping developers to quickly spot differences between complex json structures.

License: MIT License

Python 100.00%

jsoncompare's Introduction

##Install

pip install jsoncompare

##Explanation

Being able to tell whether or not an arbitrarily nested json blob is the same as another blob can hurt your eyes.
Additional complexity comes in when your json array's order doesn't matter.
For example, you might have a set in Java that you are going to send over the wire as json. It may be represented as a json array but in actuality, you don't care about the order.

Recent Changes

Version    Comments
0.1.1      Orginal Version
0.1.2      Adds support for "contains"

##Examples

from jsoncompare import jsoncompare

# Compare respecting each array's order
jsoncompare.are_same(a, b)

# Compare ignoring each array's order
jsoncompare.are_same(a, b, True)

# Compare ignoring the value of certain keys
jsoncompare.are_same(a, b, False, ["datetime", "snacktime"])

# Contains at least
jsoncompare.contains(a, b)

# Getting difference traces
from jsoncompare import jsoncompare

a = {
    "failureReason" : "Invalid request entity",
    "fieldValidationErrors" : [
        {
            "field" : "normal value 1",
            "reason" : "may not be smelly"
        },
        {
            "field" : "Catalog.name",
            "reason" : "may not be null"
        }
    ]
}
b = {
    "failureReason" : "Invalid request entity",
    "fieldValidationErrors" : [
        {
            "field" : "crazy value 2",
            "reason" : "may not be null"
        },
        {
            "field" : "Catalog.catalogOwner",
            "reason" : "may not be null"
        }
    ]
}
print jsoncompare.are_same(a, b)[1]

results in:

Reason: Different values
Expected:
  "normal value 1"
Actual:
  "crazy value 2"

Reason: Different values (Check order)
Expected:
  {
      "field": "normal value 1", 
      "reason": "may not be smelly"
  }
Actual:
  {
      "field": "crazy value 2", 
      "reason": "may not be null"
  }

Reason: Different values
Expected:
  [
      {
          "field": "normal value 1", 
          "reason": "may not be smelly"
      }, 
      {
          "field": "Catalog.name", 
          "reason": "may not be null"
      }
  ]
Actual:
  [
      {
          "field": "crazy value 2", 
          "reason": "may not be null"
      }, 
      {
          "field": "Catalog.catalogOwner", 
          "reason": "may not be null"
      }
  ]

jsoncompare's People

Contributors

Stargazers

Watchers

jsoncompare's Issues

Python 3 Support

    def _are_same(expected, actual, ignore_value_of_keys, ignore_missing_keys=False):
        # Check for None
        if expected is None:
            return expected == actual, Stack()
    
        # Ensure they are of same type
        if type(expected) != type(actual):
            return False, \
                   Stack().append(
                       StackItem('Type Mismatch: Expected Type: {0}, Actual Type: {1}'
                                    .format(type(expected), type(actual)),
                                 expected,
                                 actual))
    
        # Compare primitive types immediately
>       if type(expected) in (int, str, bool, long, float, unicode):
E       NameError: name 'long' is not defined

long is int in Python 3.

Result of comparison depends on the order of datasets being compared

This tool does not detect absolute difference between the 2 datasets.

Example:

1s.json:

{
    "Key1": "1"
}

2s.json:

{
    "Key1": "1",
    "Key2": "1"
}

$ python comparejson.py 2s.json 1s.json      
Reason: Length Mismatch: Expected Length: 2, Actual Length: 1
Expected:
  {
      "Key1": "1",
      "Key2": "2"
  }
Actual:
  {
      "Key1": "1"
  }
Missing keys: [u'Key2']
$ python comparejson.py 1s.json 2s.json
$

Is this a bug or an (undocumented) feature?

In comparison, jsondiff detects difference no matter what is the order:

$ jsondiff 1s.json 2s.json                                                                                               
{"Key2": "2"}%
$ jsondiff 2s.json 1s.json                                                                                               
{"$delete": ["Key2"]}%

scientific notation in numbers are not consider while comparing json objects

input stings :
{"_id":{"p":47272221,"c":23},"f":[{"aa":"p.E250A","fsc":1e-05}
{"_id":{"p":47272221,"c":23},"f":[{"aa":"p.E250A","fsc":0.00005}

Error:
Traceback (most recent call last):
File "jsonCompare.py", line 16, in
b=json.loads(y)
File "/usr/lib/python2.7/json/init.py", line 338, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
obj, end = self.scan_once(s, idx)
ValueError: Expecting , delimiter: line 1 column 241 (char 240)

Add license please

subj

channeliq / jsoncompare Goto Github PK

jsoncompare's Introduction

Recent Changes

jsoncompare's People

Contributors

Stargazers

Watchers

Forkers

jsoncompare's Issues

Python 3 Support

Result of comparison depends on the order of datasets being compared

scientific notation in numbers are not consider while comparing json objects

Add license please

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent