HexGrid, Hex, pathfinding.ts refactor #2461
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is largely clean up refactoring of a few files connected to
HexGrid
done in the course of reading through the files.Note
One possibly controversial thing I wanted to point out is that I deprecated a lot of "shortcut" methods in
HexGrid
.Those methods appeared to have been written before
allhexes
was added toHexGrid
. As a result of addingallhexes
, the shortcut method calls can each be replaced with a single line. That means less code and less indirection in a module that's already pretty busy. So, a good thing in my estimation.It also deprecates
forEachHex
. Usingallhexes
allows all functional JS array methods. There's not a compelling reason to keep both approaches, andallhexes
is much more flexible.To compare:
forEach
hexGrid.allhexes.forEach(hex => doSomething(hex))
hexGrid.forEachHex(hex => doSomething(hex))
filter
hexGrid.allhexes.filter(hex => isSomething(hex))
no equivalent
map
hexGrid.allhexes.map(hex => transform(hex))
no equivalent
... etc.