[Refactor] Moveset arrays can no longer hold null
values
#4919
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.
What are the changes the user will see?
N/A
Why am I making these changes?
Movesets being "allowed" to hold
null
values causes the need for lots of unnecessary extra null checks, even though if a value were actuallynull
it would break things regardless of said checks.What are the changes from a developer perspective?
The type annotations for
Pokemon.moveset
,PokemonSummonData.moveset
,PokemonData.moveset
and the return ofPokemon.getMoveset()
were updated to removenull
.How to test the changes?
npm run test
or just play the game.
Checklist
beta
as my base branchnpm run test
)[ ] Have I created new automated tests (npm run create-test
) or updated existing tests related to the PR's changes?[ ] Have I provided screenshots/videos of the changes (if applicable)?[ ] Have I made sure that any UI change works for both UI themes (default and legacy)?