refactor: improve randomization language and behavior #14
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.
Extract functionality for sorting an array into a helper method.
Make functions that are named
randomizeto return the expected randomized result. (Caller should not need to randomize the resulting array. Otherwise functions should be renamed likeselectFactionsor something.Previous implementation used
.sort(() => Math.random() - 0.5)which is a biased sorting and will favor the first element being first a higher amount of time. This is because thesortimplementation remembers previous results and will order based on them.I decided not to leverage modifying
Array.prototype. Ultimately we can easily add an extension method to a customized array subtype but I don't want to do that until we have better typing tooling which would support type coercion.