Add type checking to lang objects #1462
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.
Description and Context
Was working with the new lang objects and found another opportunity to do some type checking and reduce copy errors. With the
satisfiesoperator, we can default every function in the lang objects to expect only strings or numbers as arguments. This will help reduce accidentally passing inundefined, objects, or anything else unexpected. We can override lang functions on a case by case basis if they need to accept other types (seenoAppsElgible) - I think this is rare enough that the extra checks will be worth the slightly higher effort in those cases.Who to Notify
@brandenrodgers @joe-yeager @kemmerle