[WIP-04] [Project Solar / Phase 1 / Showcase] Add support for theming and theme-switching to the showcase #3240

didoo · 2025-09-25T20:52:01Z

Note

This PR is quite large, we may consider splitting it up in multiple PRs

📌 Summary

This PR contains multiple pieces of the "theming" puzzle:

the implementation of an hdsTheming service and a (temporary) HdsThemeSwitcher component
the implementation of a shwTheming service and set of showcase controls to switch theming (and theming options) plus the CSS file linked in the application
the implementation of a "Foundations > Theming" showcase page, plus a frameless demo page (with theme switcher) to demonstrate how theming applies to different HDS components and a mock application in general

This is based on top of #3259

🛠️ Detailed description

The first commits are a direct porting of previous showcase theming explorations (squashed):

After the initial cherry picking of code, there's been a lot of back and forth / refactorings, with different attempts in reaching an implementation that could (hopefully) withstand how different teams may want to adopt theming in their codebases. For this reason, the bulk of the work has been around finding the right "location" for the different pieces of logic, the different concerns: what goes into the HDS theming service vs the SHW theming service; how theming preferences are expressed in the UI and controlled by the user; how consumers decisions are reflected and stored and passed over between HDS/SHW services and components; how a user would use the theming controls (including a showcase user/developer/designer) and how a consumer would allow that user to interact with the application.

It's impossible to describe in detail all the code changes and implementations introduced in this PR, you have to look at diff in code, the showcase application, the "how to review" and "how to test" sections below, and try to get a general picture of what went into this PR.

👉 👉 👉 Preview: theming page

🔎 How to review

This is a quite large PR (we may consider splitting it). I would suggest to look at a piece of code/logic (eg. HDS theming service), see how this interacts with the rest of the code (in HDS and/or in the showcase), and in parallel I would try to see in the showcase application how this logic is reflected in the UI, and try to interact with it to see what happens.

The "logical" order in which I would look at things is this:

start to look at the hdsTheming service and HdsThemeSwitcher component under packages/components
move on to the shwTheming service under showCase and see how it's an extension of the hdsTheming (something we may undo, if we remove the globalOnSetTheme callback, see below)
look at the ShwThemeSwitcher controls (component and sub-components) and see how they're using internally both the hdsTheming and shwTheming services, how the "current" theming options are reflected in the services and in the controls values/states, what happens when a control value is updated/applied, etc
see how the showcase has now a small set of themed CSS variables for its colors, so it can respond to the theming changes in the controls/switchers (and how the "static" color values have been replaced across the existing pages/components)
look at the foundations/theming showcase page, and its sections
- the first one is a showcase of the HdsThemSwitcher component
- the second section is used to test how "contextual theming" (applying a theme at "local" level via a class or data attribute) works, even when nested
- the third section shows how the HDS "themed" components work (at the moment we have not decided yet how they will be handled in a themed application, but for now at least we have them collected in a single place)
- the last section is a frameless demo of a mock application with a collection of the most common HDS components
see how some of the "Mock" components and pages had to be updated, to accomodate for changes to the AppSideNav (where we've added a theme switcher) and to add even more "mock" UI elements to test with theming
look at the temporary files in the public/assets/styles/@hashicorp/ folder, in particular the CSS selectors, and see if they make sense

🛠️ How to test

Launch the showcase application locally, then visit the "Foundations > Theming" page. Here play with the controls in the top right of the page, and see how changing them impacts the page:

try to change the theming (you have multiple option groups and options, corresponding to the different way the consumers may want to adopt/use the HDS theming
try to change theming via the HDS theme switcher and see how this is reflected in the SHW controls
open the advanced options settings and see how setting/applying them see
look at the local storage in the devtools, and see how the values get updated when the different options are chose/set
look at the different sections of the theming page and see how theming and theming options apply (or don't) to them
try to apply different themes to other showcase page (in this case, since the theming tokens are only partially defined, don't expect proper theming switch, the component will look broken)

If you want to double check how the tokens and their values are applied depending on the chosen theme/options, you can update the colors in the temporary/testing CSS files under the public/assets/styles/@hashicorp/ folder (see the CSS variables under the added these to test theming in the showcase comment)

💬 To discuss/decide

do we want to swap only CSS files for the tokens, leaving the component one always the same (see [WIP-03] [Project Solar / Phase 1 / Themed CSS for HDS components] Rollup configuration and Sass processing for multiple files #3259)
is the way in which we're defining the CSS selectors correct, what we expect to be using in production? (this relates to [WIP-02] [Project Solar / Phase 1 / Tokens Pipeline] Add $modes support to tokens pipeline #3239, where we set/write the CSS selectors in the actual themed token files)
do we want to add hds-theme-system or data-hds-theme="system" when the user-selected option is system?
- pros: it's clearer what theme is applied, by looking at the HTML
- cons: it required some work to have the selector work with the :not() selectors (see below)
should the _currentStylesheet be stored in local storage or in URL as query param (same for the other shw preferences)?
do we want to keep the globalOnSetTheme callback? which use cases do we foresee?

🗒️ TODOs

write tests for the hdsTheming service
write tests for the HdsTheming component
check if we need to update/fix the CSS selector :root:not([class*="hds-theme-"],[data-hds-theme]) (it may not work, if we use hds-theme-system or data-hds-theme="system")
remove the temporary CSS files under the public/assets/styles/@hashicorp/ folder and replace them with a proper implementation based on the Ember build process
- if we decide to use only the CSS token files for the swapping, we will have to update the code accordingly
see if there is something we can get from these:
open ticket for the designers to finalize the theme switcher + engineers to implement it (maybe even more than one task, because we have to understand/decide how we will provide a way for the end-users to express their theming choice/preferences)

📸 Screenshots

Screen.Recording.2025-10-21.at.15.31.39.mov

🔗 External links

Jira tickets:

👀 Component checklist

Percy was checked for any visual regression
~~A changelog entry was added via Changesets if needed (see templates here)~~
- changelogs will be added in the main feature branch

💬 Please consider using conventional comments when reviewing this PR.

📋 PCI review checklist

If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've worked with GRC to document the impact of any changes to security controls.
Examples of changes to controls include access controls, encryption, logging, etc.
If applicable, I've worked with GRC to ensure compliance due to a significant change to the in-scope PCI environment.
Examples include changes to operating systems, ports, protocols, services, cryptography-related components, PII processing code, etc.

vercel · 2025-09-25T20:52:08Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
hds-showcase	Ready	Preview	Oct 22, 2025 5:11pm
hds-website	Ready	Preview	Oct 22, 2025 5:11pm

Copilot

Pull Request Overview

This PR implements comprehensive theming support for the HDS components library and showcase application. The implementation includes both infrastructure for theme management and UI controls for theme switching, enabling consumers to apply light/dark themes via multiple strategies (prefers-color-scheme, CSS selectors, or combined approaches).

Key changes:

Added hdsTheming service and HdsThemeSwitcher component to the HDS components library
Created shwTheming service extending hdsTheming with showcase-specific stylesheet management
Implemented showcase theming controls (ShwThemeSwitcher and sub-components) for testing different theming strategies
Added new showcase page at "Foundations > Theming" with demo components and frameless application example

Reviewed Changes

Copilot reviewed 56 out of 60 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
packages/components/src/services/hds-theming.ts	Core theming service managing theme state, local storage, and CSS selector application
packages/components/src/components/hds/theme-switcher/*	Temporary theme switcher component (dropdown-based) for light/dark/system selection
showcase/app/services/shw-theming.ts	Showcase service extending HDS theming with stylesheet swapping logic
showcase/app/components/shw/theme-switcher/*	Showcase theming controls with advanced options (modes, selectors, debugging)
showcase/app/styles/showcase-theming/*	SCSS files defining light/dark color variables for showcase UI
showcase/app/templates/page-foundations/theming/*	New theming foundation page with demo sections
showcase/app/components/mock/app/*	Updated mock components to support theme switcher integration
showcase/app/index.html	Added stylesheet links with swappable HDS components CSS

showcase/app/components/shw/theme-switcher/debugging-panel.gts

showcase/app/components/mock/app/sidebar/app-side-nav.gts

showcase/app/components/page-foundations/theming/sub-sections/contexts.gts

showcase/app/styles/showcase-theming/index.scss

packages/components/src/services/hds-theming.ts

packages/components/src/components/hds/theme-switcher/index.ts

Co-authored-by: Copilot <[email protected]>

dchyun

Overall, think the approach taken here works really well. Theme testing through the showcase theme switcher and theming page was smooth, and straightforward.

dchyun · 2025-10-21T19:44:23Z

showcase/app/components/shw/theme-switcher/popover.gts

+    }
+  };
+
+  onApplyThemingPreferences = () => {


[Issue] Somewhere in this flow the _selectedLightTheme and _selectedDarkTheme updates are not getting captured / propagated to other areas.

If my theme, via the shw themeing select, is set to "carbon / dark (g100)", and I use the settings menu to set my light and dark themes to g10 and g90.

My theme is visually updated to g90 as expected

I use the select to change to any other themes, such as "carbon / light (g10)"

My theme is incorrectly updated to the default light theme of g0

The select options all show the default light and dark options of g0 / g100

The settings menu still states my applied light and dark themes as g10 / g90 even though those aren't being applied.

yeah a bug introduced in one of the latest refactorings, I'm looking into it

Ok, main part of the bug has been fixed in c3a9268.

The fact that the selected values in the popover are out of sync with the actual values in the service is a second bug that I'll look into now

Second part fixed in 7800278 (this was a bit trickier, I had to rethink some of the logic, due to the fact that the popover element is never removed from the DOM)

dchyun · 2025-10-21T19:50:48Z

...case/public/assets/styles/@hashicorp/design-system-components-theming-with-css-selectors.css

+  --token-color-surface-faint: #ffffff;
+}
+
+.hds-theme-light,


[Question/Suggestion] Was this testing file from a previous implementation of the CSS files from the tokens? In the existing tokens PR there are no hds-{light/dark}-theme and [data-hds-theme={light/dark}] selectors.

I don't think these selectors would be feasible since a consumer could change what themes they want to use for the light and dark color schemes from the default choice of g0 and g100, but if these were included in our outputted css file like this they would always be tied to the default light and dark themes.

yes, this is still part of the experimentation we're doing, around "how we want to expose theming to our consumers". One option I'm considering is to have simpler CSS selectors (hds-{light/dark}-theme and [data-hds-theme={light/dark}]) for the "standard" use cases (in the assumption that designers will want consumers to use only two themes, as general guidance) and then find a more complex alternative (but still pre-defined by us, eg. via the combined-strategy) to let them offer to their consumers all the available themes (eg. the end-user may choose which light theme to use (between g0 and g10) and which dark one to use (between g90 and g100) for example in their settings, like you can do in GitHub for example.

In any case, something to discuss further

dchyun · 2025-10-21T20:13:10Z

showcase/app/components/shw/theme-switcher/selector.gts

+      },
+      'Theming via CSS selectors': {
+        'css-selectors|': 'HDS / Default',
+        'css-selectors|light': `Carbon / Light (${this.gLight})`,


Suggested change

'css-selectors|light': `Carbon / Light (${this.gLight})`,

'css-selectors|light|g0': `Carbon g0`,

'css-selectors|light|g10': `Carbon g10`,

'css-selectors|dark|g90': `Carbon g90`,

'css-selectors|dark|g10': `Carbon g100`,

[Suggestion] For both the css selector and combined strategy options, it could be helpful for testing purposes to switch between all of the themes with the select, instead of what is currently selected as the light and dark themes. If we had a higher number of light and dark themes it would be quicker to look through each one just with the select instead of having to go update the advanced options each time.

This is my thinking: as a showcase user (developer/designer) I would use

the "carbonized" pages (see [WIP-05] [Project Solar / Phase 1 / Showcase] Scaffolding of the showcase pages for the carbonization of the HDS components #3241) to see all at once all the possible variants, states and themes, for a component

the normal pages for more standard/simple testing (where maybe I don't need to test all the themes, expecially when all the foundations have been set, so we can "trust" the colors/themes to just work)

dchyun · 2025-10-21T20:27:57Z

showcase/app/styles/showcase-theming/index.scss

+  }
+}
+
+@media (prefers-color-scheme: dark) {


[Note] I don't have a good solution to propose for this problem, but setting the color scheme dark showcase variables for the whole showcase can make reviewing default HDS theme components more challenging, when the dev has their system set to dark mode.

I have my system set to a dark color scheme, which means my whole showcase uses the dark showcase variables even when the default HDS theme is applied which does not have a dark version.

Because all of the HDS theme options in the theme selector don't trigger the light showcase variables, the only way for me to see the HDS components on their intended lighter background is by updating my system to be light.

Maybe one solution could be using actual HDS token values here instead of hardcoded ones. Then they would still be light when no theme is applied

yeah, that's also why I was considering having an explicit hds-theme-system class or a data-hds-theme="system" attribute applied to the root (#3240 (comment))

Another consideration for using an explicit selector, is that we need to provide our consumers that want to use prefers-color-scheme a way to turn on and off the "theming" functionality (opt-in, while they have already bumped the version and imported the "themed" CSS) e.g. to do the migration incrementally, while fixing their side of the theming.

This (which I've just realized) makes me strongly think that we don't have an alternative.

dchyun · 2025-10-21T20:34:53Z

packages/components/src/services/hds-theming.ts

+    }
+
+    // store the current theme and theming options in local storage (unless undefined)
+    localStorage.setItem(


[Suggestion] There could be use cases where a consumer wants to handle on their own how they keep track of a user's theme. They could want to handle it through their own cookies or storage or some other means. It would be useful to have an argument like hasLocalStorage, where if false then nothing would get set from our service in local storage.

A consumer could then use the globalOnSetTheme to listen for theme updates and handle them in their own way.

do we want to keep the globalOnSetTheme callback? which use cases do we foresee?

Because of my point above I think it would be useful to keep the callback.

With the current implementation, what they could do would be to use the setTheme() call in the application controller, instead of the initializeTheme() (see here) and set their own theme and options; this would write on localstorage, but they could simply ignore our values and use theirs way of storing this information (as you suggested, cookie for example).

The setTheme() method has a callback, so in theory they may use that, instead of the global one, so we still have to find a good reason to keep it alive :)

Would using globalOnSetTheme be easier or more straightforward for them to use vs. setTheme() in any way?

dchyun · 2025-10-21T20:55:23Z

...case/public/assets/styles/@hashicorp/design-system-components-theming-with-css-selectors.css

do we want to add hds-theme-system or data-hds-theme="system" when the user-selected option is system?

Personally I don't think this is needed. We could say that if you are using the system theme you are then relying on the prefer-color-scheme selectors and shouldn't be trying to control that with some other selector.

I tend to agree with this.

See comment above (I am not sure it would work, but that's why I am still keeping it open as a possibility)

…meSwitcher`

…he states were potentially out of sync

this commit will be removed once we pull in `main` (after the corresponding PR is merged)

KristinLBradley · 2025-10-22T22:23:34Z

packages/components/src/services/hds-theming.ts

+}
+
+enum HdsModesBaseValues {
+  Hds = 'hds', // TODO understand if it should be `default`


If consumers don't do anything, the "Hds" theme is the one they should get so that would be a "default". Is that what you mean?

KristinLBradley · 2025-10-22T22:26:44Z

packages/components/src/services/hds-theming.ts

+
+enum HdsModesDarkValues {
+  CdsG90 = 'cds-g90',
+  CdsG100 = 'cds-g100',


I still don't really understand the purpose of having multiple Light & Dark value options.

KristinLBradley · 2025-10-22T22:39:36Z

packages/components/src/services/hds-theming.ts

+export default class HdsThemingService extends Service {
+  @tracked _isInitialized: boolean = false;
+  @tracked _currentTheme: HdsThemes | undefined = undefined;
+  @tracked _currentMode: HdsModes = undefined;


Would it be clearer to include "undefined" for the type here (vs. including it in the type definition above) the same way it's defined for _currentTheme or is that a dumb question? (Or change the type definition for HdsThemes?)

(i.e. use HdsModes | undefined = undefined;)

KristinLBradley · 2025-10-22T23:38:12Z

showcase/app/services/shw-theming.ts

+        'assets/styles/@hashicorp/design-system-components-theming-with-combined-strategies.css';
+      break;
+    default:
+      // this is the standard CSS for HDS components, without any theming


Suggested change

// this is the standard CSS for HDS components, without any theming

// this is the "standard" CSS for HDS components, without any theming

(just to make it stand out a bit more clearly)

hashibot-hds added packages/components packages/tokens showcase labels Sep 25, 2025

vercel bot deployed to Preview – hds-website September 25, 2025 20:53 View deployment

didoo mentioned this pull request Sep 25, 2025

[WIP-05] [Project Solar / Phase 1 / Showcase] Scaffolding of the showcase pages for the carbonization of the HDS components #3241

Open

8 tasks

didoo changed the title ~~[WIP] [Project Solaris / Phase 1 / Showcase] Add support for theming and theme-switching to the showcase~~ [WIP] [Project Solis / Phase 1 / Showcase] Add support for theming and theme-switching to the showcase Sep 25, 2025

didoo changed the title ~~[WIP] [Project Solis / Phase 1 / Showcase] Add support for theming and theme-switching to the showcase~~ [WIP] [Project Solar/ Phase 1 / Showcase] Add support for theming and theme-switching to the showcase Sep 25, 2025

didoo changed the title ~~[WIP] [Project Solar/ Phase 1 / Showcase] Add support for theming and theme-switching to the showcase~~ [WIP] [Project Solar / Phase 1 / Showcase] Add support for theming and theme-switching to the showcase Sep 25, 2025

didoo added the project solar label Sep 26, 2025

didoo force-pushed the project-solar/phase-1/HDS-5242_showcase/add-themes-support branch from b73dbf9 to a4f41dd Compare September 30, 2025 14:11

vercel bot had a problem deploying to Preview – hds-showcase September 30, 2025 14:11 Failure

vercel bot had a problem deploying to Preview – hds-website September 30, 2025 14:11 Failure

didoo force-pushed the project-solar/phase-1/HDS-5242_showcase/add-themes-support branch from a4f41dd to cc61972 Compare September 30, 2025 14:20

vercel bot had a problem deploying to Preview – hds-showcase September 30, 2025 14:20 Failure

vercel bot had a problem deploying to Preview – hds-website September 30, 2025 14:20 Failure

didoo force-pushed the project-solar/phase-1-main-feature-branch branch from 519a6a6 to 3863dfa Compare September 30, 2025 14:50

didoo force-pushed the project-solar/phase-1/HDS-5242_showcase/add-themes-support branch from cc61972 to 59418c1 Compare September 30, 2025 16:16

vercel bot had a problem deploying to Preview – hds-showcase September 30, 2025 16:16 Failure

vercel bot had a problem deploying to Preview – hds-website September 30, 2025 16:16 Failure

didoo force-pushed the project-solar/phase-1/HDS-5242_showcase/add-themes-support branch from 59418c1 to 2f20cdc Compare September 30, 2025 17:23

vercel bot had a problem deploying to Preview – hds-showcase September 30, 2025 17:23 Failure

vercel bot had a problem deploying to Preview – hds-website September 30, 2025 17:23 Failure

didoo force-pushed the project-solar/phase-1/HDS-5242_showcase/add-themes-support branch from 2f20cdc to 92910be Compare September 30, 2025 17:23

vercel bot had a problem deploying to Preview – hds-website September 30, 2025 17:23 Failure

vercel bot had a problem deploying to Preview – hds-showcase September 30, 2025 17:23 Failure

didoo force-pushed the project-solar/phase-1/HDS-5242_showcase/add-themes-support branch from 92910be to a1ff2f5 Compare September 30, 2025 20:23

vercel bot had a problem deploying to Preview – hds-website September 30, 2025 20:23 Failure

vercel bot had a problem deploying to Preview – hds-showcase September 30, 2025 20:23 Failure

vercel bot had a problem deploying to Preview – hds-showcase October 1, 2025 15:08 Failure

vercel bot deployed to Preview – hds-showcase October 21, 2025 13:34 View deployment

vercel bot deployed to Preview – hds-website October 21, 2025 13:37 View deployment

didoo requested review from KristinLBradley, Copilot and dchyun October 21, 2025 15:17

didoo marked this pull request as ready for review October 21, 2025 15:17

didoo requested a review from a team as a code owner October 21, 2025 15:17

Copilot AI reviewed Oct 21, 2025

View reviewed changes

didoo added 3 commits October 21, 2025 16:28

refactor and cleanup in preparation for PR review

b6ad465

refactored code to fix logic flow for theming initialization

8c6da52

fixed how the theming options were saved in local storage

25c5e29

didoo force-pushed the project-solar/phase-1/HDS-5242_showcase/add-themes-support branch from d3239c3 to 25c5e29 Compare October 21, 2025 15:28

vercel bot deployed to Preview – hds-showcase October 21, 2025 15:29 View deployment

vercel bot deployed to Preview – hds-website October 21, 2025 15:32 View deployment

Apply suggestions from Copilot's code review

4d45460

Co-authored-by: Copilot <[email protected]>

vercel bot deployed to Preview – hds-showcase October 21, 2025 15:44 View deployment

vercel bot deployed to Preview – hds-website October 21, 2025 15:47 View deployment

didoo mentioned this pull request Oct 21, 2025

[WIP-03] [Project Solar / Phase 1 / Themed CSS for HDS components] Rollup configuration and Sass processing for multiple files #3259

Open

7 tasks

dchyun reviewed Oct 21, 2025

View reviewed changes

fixed issue with setTheme not being passed options by the `ShwThe…

c3a9268

…meSwitcher`

vercel bot deployed to Preview – hds-showcase October 22, 2025 14:12 View deployment

vercel bot deployed to Preview – hds-website October 22, 2025 14:14 View deployment

didoo added 2 commits October 22, 2025 18:07

fix issue with the popover of the ShwThemeSwitcher component, where t…

7800278

…he states were potentially out of sync

TEMP - silence deprecations

85beb6f

this commit will be removed once we pull in `main` (after the corresponding PR is merged)

vercel bot deployed to Preview – hds-showcase October 22, 2025 17:09 View deployment

vercel bot deployed to Preview – hds-website October 22, 2025 17:11 View deployment

KristinLBradley reviewed Oct 22, 2025

View reviewed changes

-        'css-selectors|light': `Carbon / Light (${this.gLight})`,
+        'css-selectors|light|g0': `Carbon g0`,
+        'css-selectors|light|g10': `Carbon g10`,
+        'css-selectors|dark|g90': `Carbon g90`,
+        'css-selectors|dark|g10': `Carbon g100`,

	// this is the standard CSS for HDS components, without any theming
	// this is the "standard" CSS for HDS components, without any theming

[WIP-04] [Project Solar / Phase 1 / Showcase] Add support for theming and theme-switching to the showcase #3240

Are you sure you want to change the base?

[WIP-04] [Project Solar / Phase 1 / Showcase] Add support for theming and theme-switching to the showcase #3240

Conversation

didoo commented Sep 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📌 Summary

🛠️ Detailed description

🔎 How to review

🛠️ How to test

💬 To discuss/decide

🗒️ TODOs

📸 Screenshots

🔗 External links

👀 Component checklist

Uh oh!

vercel bot commented Sep 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Key changes:

Reviewed Changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

dchyun left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

didoo Oct 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

didoo Oct 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

didoo commented Sep 25, 2025 •

edited

Loading

vercel bot commented Sep 25, 2025 •

edited

Loading

didoo Oct 22, 2025 •

edited

Loading

didoo Oct 22, 2025 •

edited

Loading