studio: read an allowlisted admin as PRO on its own, so a rollout that pairs this bundle with an older API cannot show the operator the basic-tier bar
This commit is contained in:
@@ -551,7 +551,10 @@ export function Workspace() {
|
||||
// GRADIENT MASK, RAW, and an export past the photo's own pixels. An
|
||||
// allowlisted admin is the operator, so it counts as PRO by construction.
|
||||
const member = !!user;
|
||||
const pro = !!user?.pro;
|
||||
// `admin` as well as `pro`: the server already answers PRO for an allowlisted
|
||||
// operator, but a deployment mid-rollout can serve an API older than this
|
||||
// bundle, and the operator must never be the one account that reads as basic.
|
||||
const pro = !!user?.pro || !!user?.admin;
|
||||
// The export ceiling the menu and the file both obey: none for PRO, the
|
||||
// photo's own long edge for a basic account, the tier's 2048 for a guest.
|
||||
const exportCap = pro ? null : member ? editedLongest : TIERS.guest.maxExportDim;
|
||||
|
||||
Reference in New Issue
Block a user