Type Alias Platformstreamers<T, P>

Type declaration

• currentTotal: number

• maxLimit: number

• premium: {
      tierId: string;
      tierName: string;
  }

  • tierId: string

  • tierName: string

• streamers: P extends ServedPlatform
      ? (T extends true
          ? Pick<GuildSingleStreamer<P>, Extract<keyof GuildSingleStreamer<P>, ShortViewKeySets[P]>>
          : GuildSingleStreamer<P>)[]
      : never

  shortView: true gives the projection named in ShortViewKeySets; false gives the whole streamer, exactly as GuildSingleStreamer<P> defines it.

  Both halves are DERIVED rather than listed again, because listing them again is precisely what broke. The two guards above GuildSingleStreamer hold the platform enum and the bundled Prisma models together in both directions; a third list written out by hand sat outside both of them and drifted from each.

  The zod family is deliberate, and it is not a matter of taste. KickStreamerZod is RemoveProperties<TSPrismaModelsFull['KickStreamer'], KickStreamerRelations> - the Prisma model minus the back-reference objects, recursively. The API answers this route with rows from a findMany, which carry forward relations but no back-pointers, so the Prisma-derived type CLAIMS members the response does not contain. A claimed-but-absent field reads undefined at runtime and typechecks clean, which is the whole family of bug this type already shipped twice. The zod type under-claims instead (it also drops the relation FK scalars), and under-claiming cannot be read by accident.

• OptionalthumbnailWaitBaselineSeconds?: number

  The baseline every creator already gets, in seconds - the number thumbnailWaitOptions ADD to.

  Use this to label a control honestly: option 30 with a baseline of 10 is "+30s (up to 40s)", and null is "no extra time (10s baseline)", NOT "do not wait".

  Do not hard-code the ten. It is derived server-side from the thumbnail probe budget, which is environment-tunable, so a copied literal silently overstates the ceiling the day it is changed. Absent on APIs that predate this field - fall back to 10 there, and only there.

• OptionalthumbnailWaitOptions?: number[]

  The values thumbnailWaitSeconds will accept, served by the API. Kick only.

  EXTRA seconds on top of the ten second baseline every creator already gets, NOT a total - see THUMBNAIL_WAIT_CHOICES below before you write the control's label.

  Prefer this over the THUMBNAIL_WAIT_CHOICES constant. This is the authority; the constant is a hand-copy kept for APIs that predate this field. Absent on those - fall back to the constant.