Ignore fields parameter in assert methods

[nadaj]

Fixed issue: #21

Added parameter to assert methods that can ignore single or multiple fields (given as a list) in snapshot.

[bsod90]

This won't work with nested fields, right?
something like

{
    "content": {
        "created_at": "......."
    }
}

[nadaj]

You're right, in this case it will not work. What do you suggest in this case since we can have a situation like this:

{
    "created_at": ... ,
    "content": {
        "created_at": "......."
    }
}

Should the remove_fields parameter perhaps be a list if we would want to separate these cases? In this example if you wanted to delete the non-nested created_at you could just pass 'created_at' or ['created_at'] and for the nested ['content', 'created_at'].

The second option would be to globally remove the given field, so if 'created_at' is given as the parameter, it should remove every appearance of it (including nested).

[bsod90]

Right. I'm not quite sure myself on what to do in this situation. One approach would be to specify not just keys but the whole path, kind of like "content.items.*.event.created_at" however, for my needs, I just forked this repo and made it delete every key that matches the name recursively.

[ish-vasa]

@bsod90 @nadaj --> any plans to push this through or can i pick it up?

[josephtyler]

This would be a nice feature to have.

[HeyHugo]

Nice!

It would be nice if you still asserted the keys exist before removing them. I.e we ignore what is rendered for the ignored fields but still assert that they are present.

[gurunars]

Duplicates this one: #102

And I would say that it should be treated similarly.