bug: mapped grids don't behave as described

I’m using 4.0.0-alpha.5

I tried this simple code snippet: https://github.com/flauwekeul/honeycomb/tree/next#controlling-how-hexes-are-created

It doesn’t seem to work, as demonstrated here: https://stackblitz.com/edit/js-xjvkfz?devToolsHeight=33&file=index.js

What happens is that instead of the following:

// ...
grid.getHex([1, 2])       // Hex {q: 1, r: 2}
mappedGrid.getHex([1, 2]) // Hex {q: 1, r: 2, custom: 'custom'}

We get this:

// ...
grid.getHex([1, 2])       // Hex {q: 1, r: 2}
mappedGrid.getHex([1, 2]) // Hex {q: 1, r: 2}

Since it clearly deviates from the stated behaviour I’d imagine it’s a bug? If not, it’d be nice to understand what the behaviour should actually be.

[israelidanny]

You’re a legend @flauwekeul

[flauwekeul]

Great 😀 I just pushed another example that happens to showcase (nearly complete) A* path finding using Honeycomb.

I’ll close this issue then.

P.S. Please let me know if you find any more issues or think things are counter intuitive or if you need certain features. Thanks!