This repository has been archived by the owner on Aug 16, 2024. It is now read-only.
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.
Previously, sponsor tiers were inserted when the app was created and that ordering of database object IDs was used to determine (sometimes contextually incorrect) order.
This PR adds a new field on the
SponsorTier
snippet which allows us to define a "priority". The tiers (within the category) are then ordered by the inverse of this priority on the page. Meaning, tiers with higher priority are shown higher in the page. I've tested this locally and asserted that a "super diamond" tier with a higher priority than 0 shows up above Diamond, even though the latter was added first.Because the priority is also an arbitrary number, we can just choose increments of 10 in case we add any other tiers in between!