improvement: Update lookupLimit function to use nullish coalescing fo… #20
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.
In order to avoid running
updateOrg()
on existing users, triggering a re-creation of Stripe customers, leading to duplicates, I've added the metadatatier.org = "org:user_xyz"
to existing Stripe customers.This successfully make Tier recognize the user. However, when running
tier.can()
, I get:Hence, I've added nullish coalescing for more precise default handling.