Follow-up from "Add self managed trial widget"

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Label this issue

The following discussions from !209831 (merged) should be addressed:

@dstull started a discussion:

note (non-blocking):

key for TRIAL_TYPES_CONFIG in frontend.

I wonder if moving this SSOT to the backend will enable us to not have a split concept with backend or frontend being a SSOT in the widget.

To be explored in a follow-up
@markrian started a discussion:

thought (non-blocking): Out of scope for this MR, but the image in the Discover Premium with Duo Core page doesn't look like a link to a video, but it is. Perhaps the thumbnail could be changed to make it look like a video? Or the video could be embedded?

simplescreenrecorder-2025-10-29_10.56.38

suggestion (non-blocking): These can be camelCased, and dismisserProps would be a more accurate name:

    dismisserProps() {
      return {
        featureName: this.featureId,
        skipQuery: true,
        ...(this.groupId && { groupId: this.groupId }),
      };
    },

@markrian started a discussion:
nitpick (non-blocking): This should probably use makeMockUserCalloutDismisser instead.
```
        UserCalloutDismisser: makeMockUserCalloutDismisser(mockCalloutOptions),
```
@markrian started a discussion:

question (non-blocking): What's the use case for these examples?

If there's no feature name given, then surely the GraphQL request would fail?

Or is it that the trial widget is only rendered if it has a featureId? Except, I see that the isDismissible computed is based on the truthiness of the featureId 🤔

Okay, I think I get it now: skipQuery is always true, so there's no query. And a mutation is only sent when dismiss is called, which it cannot be if there's no featureId. Right?

Edited Oct 29, 2025 by 🤖 GitLab Bot 🤖