Add optional resource getters to World - #362
Merged
Merged
Conversation
waynemwashuma
force-pushed
the
optional-resource
branch
from
August 26, 2026 05:04
4ca3730 to
fcf1a86
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Objective
Introduce optional resource getters that allow resources to be retrieved without throwing when they do not exist.
Solution
Added optional variants of the
Worldresource getter APIs while preserving resource alias resolution.Changes Made
World.getOptionalResource()for type-based lookups.World.getOptionalResourceByTypeId()for type ID lookups.Why This Approach
Required getters continue to assert when a resource is missing, while optional getters return
undefined.Showcase
Before
After
Migration Guide
No migration required.
Checklist