What purpose do the serialized keys of a Mesh mean?

Questions
, , ,
1

I’m trying to work on a way for developing unit tests for a library I’m working on that uses Babylon. My first thought is to have every object carry a Mesh member, then use NullEngine and Babylon’s serializer to make a text representation of each and use asserts and snapshots. The problem is that every the serialized meshes are massive, which makes them impractical for snapshots.

Can someone please explain the purpose of each member of a serialized mesh is and which ones are considered essential?

2

Can you provide detail on “every object” and “massive?” Providing a PG for your issue would be enlightening.

3

As they have been added manually, they are all essential for deserializing from the babylon file format.

Also serialization might change from version to version, why not asserting only the properties you would need ?

4

That’s kind of like

mesh.position = new Vector3(1, 1, 1);
assert(mesh.position.x === 1);

It doesn’t tell you much.