Configure serializer to skip element attributes on snapshot.

[dzhytomyrsky]

Hello is it possible to configure serializer to skip element attributes? It would be wonderful to get on snapshot only elements and innerText.

<ul
  className="bottomMasked"
  id="agentsList"
  onScroll={[Function]}
>
  <li
    className={null}
    onClick={[Function]}
>
    Detective Inspector Lee
  </li>
</ul>

[runk]

Would be awesome to have this feature. 💯

[JonathanTR]

What would it look to configure this? Maybe something like?:

import serializer from 'enzyme-to-json/serializer';
import Foo        from './Foo'

const compactSerializer = serializer.withExceptions([<ul />, <Foo />]);
expect.addSnapshotSerializer(compactSerializer);

[adriantoine]

Hi!

Thanks for your suggestions, would you mind giving more details about that? I don't think I understand, you want a snapshot with only elements and inner texts?

enzyme-to-json is only converting Enzyme wrappers to a JSON format that is compatible with Jest snapshot testing. Isn't that something you want to be implemented in Jest so that it is available for people only using react-test-renderer?

[JonathanTR]

Ah, I'm realizing that what I wanted was actually quite different from OP, as I had read their post pretty quickly. What I was thinking was something more along the lines of being able to collapse certain elements within a snapshot.

So instead of having:

<Button
  color="blue"
>
  <button
    className="button blue"
  >
  </button>
</Button>

I could configure my serializer to just return something like:

<Button
  color="blue"
>
  { [children] }
</Button>

This would be awesome for cleaning up snapshots, especially in cases where there's lots of HOC's wrapped up in an implementation. Being able to configure whether I wanted inline props or not would be even more cool, so I could end up with a beautiful snapshot like:

<Button color="blue">
  { [children] }
</Button>

[adriantoine]

I'm working on a map functionality (see #48) which would give much more control on the output. It will be released with v3.0.0.

I'm not sure about the details of the implementation but I'll give more details in #67 as soon as I can.

Thanks for your suggestions!

[adriantoine]

@JonathanTR @dzhytomyrsky @runk I just added a comment to #67 about this new mapping functionality, can you tell me if it solves your issue?

Thanks!

[adriantoine]

v3.0.0 has been released 🎉, the map functionality should cover this use case, if not, please comment on this issue!