chore: Expose premiumStatus user field
#382
Merged
Conversation
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
src/types/entities.ts
Outdated
| avatarSmall: z.string().nullish(), | ||
| businessAccountId: z.string().nullable(), | ||
| isPremium: z.boolean(), | ||
| premiumStatus: z.string(), |
Contributor
There was a problem hiding this comment.
If we already know what all the values will be, could we not make this an enum type?
Contributor
Author
There was a problem hiding this comment.
I was about to say that we don't use enums in this schema anywhere, but that's not true because we do that for workspace role, workspace plan, workspace plan status, upload status, etc.
The only downside is that if we ever want to add some enum values for this field we'd have to open a PR against this repo to add the new field, however 1. I don't think that'll be very often, 2. it's not that much work 😅
Hence, I'll update this PR now to switch to the enum type 👍
scottlovegrove
force-pushed
the
francesca/expose-premium-status
branch
from
43f92bf to
5b48ca5
Compare
scottlovegrove
approved these changes
Nov 10, 2025
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.
As part of our current "Pro Legacy" effort (as in: we'll move some old Pro users to a new limited plan called Pro Legacy, which will have limited features, i.e. it won't have access to our AI Assistant extension), I need/want to make our AI Assistant extension aware of a more granular attribute based on which to determine if the user should have access to the AI Assistant extension:
premium_status.In fact, looking at
premium_status, we'll be able to make sure that we only allow users whenpremium_statusis eithercurrent_personal_planorteams_business_memberbut not if it'slegacy_personal_planornot_premium. The AI Assistant change is drafted in https://github.com/Doist/event-integrations/pull/2269 but needstodoist-api-typescriptto start returningpremiumStatus, which it's what this current PR does.Backend refs:
Refs: