Adding new slots for Notification Tray integration #644

farhaanbukhsh · 2025-10-12T07:25:40Z

Addition of the Header Item slot, this slot is created with the intention to add Notitification Tray to the learner dashboard, studio, and learning MFE. This in turn helps to add the same slot to other MFEs as well since all of them use the same header.

JIRA tickets: None

Discussions: Link to any public dicussions about this PR or the design/architecture. Otherwise omit this.

Dependencies: None

Screenshots:

Included in the Readme.md

Sandbox URL: TBD - sandbox is being provisioned.

Merge deadline: "None" if there's no rush, "ASAP" if it's critical, or provide a specific date if there is one.

Testing instructions:

Clone this repo and change to this branch. Run npm ci && npm run build
Let's checkout the learner dashboard to have the notification tray slot.
If you have a tutor devstack already running, stop the learner dashboard, tutor dev stop learner-dashboard
Make sure learner-dashboard is already mounted you can check tutor mount lists if is is not mounted you can add tutor mounts add /path_to/edx-devstack/frontend-app-learner-dashboard and build the image tutor images build openedx-dev
Now we need to copy the dist/ folder under frontend-component-header. cp -r /path_to/edx-devstack/frontend-component-header/dist /path_to/edx-devstack/frontend-app-learner-dashboard/node_modules/@edx/frontend-component-header. This copies the built codebase to the frontend-component-header
Add env.config.jsx in /path_to/edx-devstack/frontend-app-learner-dashboard with the content,

import { PLUGIN_OPERATIONS, DIRECT_PLUGIN } from '@openedx/frontend-plugin-framework';
import { NotificationsTray, useAppNotifications, Notifications } from '@edx/frontend-plugin-notifications';
// Load environment variables from .env file
const config = {
  pluginSlots: {
    "org.openedx.frontend.layout.desktop_header_item_slot.v1": {
      keepDefault: false,
      plugins: [
        {
          op: PLUGIN_OPERATIONS.Insert,
          widget: {
            id: 'custom_notification_tray',
            type: DIRECT_PLUGIN,
            RenderWidget: () => (
              <NotificationsTray />
            ),
          },
        },
      ],
    },
  },
};

export default config;

We need to install the notification plugin in learner dashboard i.e /path_to/edx-devstack/frontend-app-learner-dashboard npm i @edx/frontend-plugin-notifications@^2.0.3
Now we can run npm run dev, after this if we see learner dashboard we should see notification icon button.
Similar configs can be created for other MFEs to test them locally.

openedx-webhooks · 2025-10-12T07:25:45Z

Thanks for the pull request, @farhaanbukhsh!

This repository is currently maintained by @openedx/committers-frontend.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
- This process (including the steps you'll need to take) is documented here.
If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

Dependencies

This PR must be merged before / after / at the same time as ...
Blockers

This PR is waiting for OEP-1234 to be accepted.
Timeline information

This PR must be merged by XX date because ...
Partner information

This is for a course on edx.org.
Supporting documentation
Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

The size and impact of the changes that it introduces
The need for product review
Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

codecov · 2025-10-12T11:01:05Z

Codecov Report

❌ Patch coverage is 90.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 72.40%. Comparing base (dbec796) to head (ed08e48).
⚠️ Report is 17 commits behind head on master.

Files with missing lines	Patch %	Lines
src/plugin-slots/MobileHeaderItemSlot/index.jsx	50.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #644      +/-   ##
==========================================
- Coverage   73.01%   72.40%   -0.61%     
==========================================
  Files          55       59       +4     
  Lines         504      511       +7     
  Branches      100      108       +8     
==========================================
+ Hits          368      370       +2     
- Misses        133      138       +5     
  Partials        3        3

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Signed-off-by: Farhaan Bukhsh <[email protected]>

tecoholic

@farhaanbukhsh Great work on handling the multiple scenarios here. Thanks for the detailed testing instructions. I followed them and they mostly worked except for the <NotificationsTray /> component never showing up. I change to simple span like the ones from the README and that worked just fine.

I have left inline comments. I want to note a couple of things that I noticed here:

Missing `priority` in the `widget` definitions

When I inpect the component tree in React Dev tools, I have this error on the slot, for all the slots

the insert operation config is invalid for widget id: mobile_notification_tray undefined

this error goes away only when the priority key is added to the widget object. So, all the code examples in the README file will need to be updated to include this property.

JSX `key` spread warning

There is also another error in the component tree with an ErrorBoundary

Warning: A props object containing a "key" prop is being spread into JSX: let props = {key: someKey, id: ...}; <RenderWidget {...props} /> React keys must be passed directly to JSX without using spread: let props = {id: ...}; <RenderWidget key={someKey} {...props} /> at PluginContainerDirect (webpack-internal:///./node_modules/@openedx/frontend-plugin-framework/dist/plugins/PluginContainerDirect.js:25:7) at ErrorBoundary (webpack-internal:///./node_modules/@edx/frontend-platform/react/ErrorBoundary.js:104:5) at PluginContainer (webpack-internal:///./node_modules/@openedx/frontend-plugin-framework/dist/plugins/PluginContainer.js:27:7) at BasePluginSlot (webpack-internal:///./node_modules/@openedx/frontend-plugin-framework/dist/plugins/PluginSlot.js:31:7) at MobileHeaderItemSlot at button at MenuTrigger (webpack-internal:///./node_modules/@edx/frontend-component-header/dist/Menu/Menu.js:146:18) at nav at Menu (webpack-internal:///./node_modules/@edx/frontend-component-header/dist/Menu/Menu.js:196:5) at div at header at MobileHeader (webpack-internal:///./node_modules/@edx/frontend-component-header/dist/mobile-header/MobileHeader.js:82:23) at BasePluginSlot (webpack-internal:///./node_modules/@openedx/frontend-plugin-framework/dist/plugins/PluginSlot.js:31:7) at MobileHeaderSlot (webpack-internal:///./node_modules/@edx/frontend-component-header/dist/plugin-slots/MobileHeaderSlot/index.js:13:20) at MediaQuery (webpack-internal:///./node_modules/react-responsive/dist/react-responsive.js:868:33) at Header (webpack-internal:///./node_modules/@edx/frontend-component-header/dist/Header.js:77:28) at LearnerDashboardHeader (webpack-internal:///./src/containers/LearnerDashboardHeader/index.jsx:36:52) at AppWrapper (webpack-internal:///./src/containers/AppWrapper/index.jsx:15:5) at div at App (webpack-internal:///./src/App.jsx:64:52) at PageWrap (webpack-internal:///./node_modules/@edx/frontend-platform/react/PageWrap.js:25:23) at RenderedRoute (webpack-internal:///./node_modules/react-router/dist/index.js:579:5) at Routes (webpack-internal:///./node_modules/react-router/dist/index.js:1313:5) at div at NoticesWrapper (webpack-internal:///./src/components/NoticesWrapper/index.jsx:30:5) at div at Router (webpack-internal:///./node_modules/react-router/dist/index.js:1247:15) at BrowserRouter (webpack-internal:///./node_modules/react-router-dom/dist/index.js:704:5) at div at Provider (webpack-internal:///./node_modules/react-redux/es/components/Provider.js:19:20) at OptionalReduxProvider (webpack-internal:///./node_modules/@edx/frontend-platform/react/OptionalReduxProvider.js:19:25) at ErrorBoundary (webpack-internal:///./node_modules/@edx/frontend-platform/react/ErrorBoundary.js:104:5) at IntlProvider (webpack-internal:///./node_modules/react-intl/lib/src/components/provider.js:42:47) at AppProvider (webpack-internal:///./node_modules/@edx/frontend-platform/react/AppProvider.js:117:25)

I am NOT certain about the reason for this error, but I suspect it's probably connected to not defining any properties in the slots. Thus, making the plugin-slots library's implementation do something that React doesn't like.

tecoholic · 2025-10-13T02:51:25Z

src/mobile-header/MobileHeader.jsx

+            <MenuTrigger
+              tag="button"
+              className="icon-button"
+              aria-label={intl.formatMessage(messages['header.label.mobile.item.slot'])}
+              title={intl.formatMessage(messages['header.label.mobile.item.slot'])}
+            >
+              {renderMobileHeaderItemSlot()}
+            </MenuTrigger>


Suggested change

<MenuTrigger

tag="button"

className="icon-button"

aria-label={intl.formatMessage(messages['header.label.mobile.item.slot'])}

title={intl.formatMessage(messages['header.label.mobile.item.slot'])}

>

{renderMobileHeaderItemSlot()}

</MenuTrigger>

<MobileHeaderItemSlot />

Otherwise the MenuTrigger would act on the both the UserIcon and the slot. For example, notice the menu opening for the "MOB" button.

tecoholic · 2025-10-13T02:54:27Z

src/plugin-slots/DesktopHeaderItemSlot/images/learner_dashboard_notification.png

This image doesn't correspond to the code in the example. So, it might be a bit confusing for the reader to notice the change.

tecoholic · 2025-10-13T02:56:07Z

src/plugin-slots/LearningHeaderItemSlot/images/learner_header_notification.png

Same feeback as the previous screenshot. We either need to show the same content, so it matches or mark the slot in the picture so, the reader knows where to expect the content.

tecoholic · 2025-10-13T03:03:31Z

src/plugin-slots/DesktopHeaderItemSlot/README.md

+The slot is kept empty so that it can only be enabled when it is required else
+nothing is displayed. It is used to add item in the frontend-app-learner-dashboard
+header.


The slot is named as DesktopHeaderItemSlot, but here it is mentioned it only adds an item in the learner-dashboard MFE. Shouldn't it them be LearnerDashboardHeaderItemSlot following the convention of StudioHeaderItemSlot LearningHeaderItemSlot..etc.,?

Or does this slot apply to all the other MFEs that doesn't have specific headers like Studio & Learning MFE?

Either way, a description of what this slot is, with specifics on where it does & doesn't apply would be better here.

it's mostly the slots which doesn't have any specific header @tecoholic I have changed it to match other Readme under same heading.

tecoholic · 2025-10-13T03:04:48Z

src/desktop-header/DesktopHeader.jsx

            {loggedIn
              ? (
                <>
+                  {renderDesktopHeaderItemSlot()}


Any specific reason not to simply do this?

Suggested change

{renderDesktopHeaderItemSlot()}

<DesktopHeaderItemSlot />

tecoholic · 2025-10-13T03:07:36Z

src/__snapshots__/Header.test.jsx.snap

      onMouseEnter={[Function]}
      onMouseLeave={[Function]}
    >
+      <button


I think this shouldn't be needed here and it probably an artifact due to the MenuTrigger wrapper in the MobileHeader.jsx below.

tecoholic · 2025-10-13T03:08:33Z

src/Header.messages.jsx

+  'header.label.mobile.item.slot': {
+    id: 'header.label.mobile.item.slot',
+    defaultMessage: 'Mobile Item Slot',
+    description: 'The aria label for plugin item slot for mobile',
+  },


If this is specific to the Header tests, then this shouldn't be needed when the MenuTrigger is removed.

farhaanbukhsh · 2025-10-13T10:40:31Z

@farhaanbukhsh Great work on handling the multiple scenarios here. Thanks for the detailed testing instructions. I followed them and they mostly worked except for the <NotificationsTray /> component never showing up. I change to simple span like the ones from the README and that worked just fine.

npm i @edx/frontend-plugin-notifications@^2.0.3 should solve it possibly the npm directly pulled from github and didn't run a build on it.

I have left inline comments. I want to note a couple of things that I noticed here:

Missing priority in the widget definitions

When I inpect the component tree in React Dev tools, I have this error on the slot, for all the slots
the insert operation config is invalid for widget id: mobile_notification_tray undefined
this error goes away only when the priority key is added to the widget object. So, all the code examples in the README file will need to be updated to include this property.

Great I will add the priority to the readme.md @tecoholic

JSX `key` spread warning

There is also another error in the component tree with an ErrorBoundary

Warning: A props object containing a "key" prop is being spread into JSX: let props = {key: someKey, id: ...}; <RenderWidget {...props} /> React keys must be passed directly to JSX without using spread: let props = {id: ...}; <RenderWidget key={someKey} {...props} /> at PluginContainerDirect (webpack-internal:///./node_modules/@openedx/frontend-plugin-framework/dist/plugins/PluginContainerDirect.js:25:7) at ErrorBoundary (webpack-internal:///./node_modules/@edx/frontend-platform/react/ErrorBoundary.js:104:5) at PluginContainer (webpack-internal:///./node_modules/@openedx/frontend-plugin-framework/dist/plugins/PluginContainer.js:27:7) at BasePluginSlot (webpack-internal:///./node_modules/@openedx/frontend-plugin-framework/dist/plugins/PluginSlot.js:31:7) at MobileHeaderItemSlot at button at MenuTrigger (webpack-internal:///./node_modules/@edx/frontend-component-header/dist/Menu/Menu.js:146:18) at nav at Menu (webpack-internal:///./node_modules/@edx/frontend-component-header/dist/Menu/Menu.js:196:5) at div at header at MobileHeader (webpack-internal:///./node_modules/@edx/frontend-component-header/dist/mobile-header/MobileHeader.js:82:23) at BasePluginSlot (webpack-internal:///./node_modules/@openedx/frontend-plugin-framework/dist/plugins/PluginSlot.js:31:7) at MobileHeaderSlot (webpack-internal:///./node_modules/@edx/frontend-component-header/dist/plugin-slots/MobileHeaderSlot/index.js:13:20) at MediaQuery (webpack-internal:///./node_modules/react-responsive/dist/react-responsive.js:868:33) at Header (webpack-internal:///./node_modules/@edx/frontend-component-header/dist/Header.js:77:28) at LearnerDashboardHeader (webpack-internal:///./src/containers/LearnerDashboardHeader/index.jsx:36:52) at AppWrapper (webpack-internal:///./src/containers/AppWrapper/index.jsx:15:5) at div at App (webpack-internal:///./src/App.jsx:64:52) at PageWrap (webpack-internal:///./node_modules/@edx/frontend-platform/react/PageWrap.js:25:23) at RenderedRoute (webpack-internal:///./node_modules/react-router/dist/index.js:579:5) at Routes (webpack-internal:///./node_modules/react-router/dist/index.js:1313:5) at div at NoticesWrapper (webpack-internal:///./src/components/NoticesWrapper/index.jsx:30:5) at div at Router (webpack-internal:///./node_modules/react-router/dist/index.js:1247:15) at BrowserRouter (webpack-internal:///./node_modules/react-router-dom/dist/index.js:704:5) at div at Provider (webpack-internal:///./node_modules/react-redux/es/components/Provider.js:19:20) at OptionalReduxProvider (webpack-internal:///./node_modules/@edx/frontend-platform/react/OptionalReduxProvider.js:19:25) at ErrorBoundary (webpack-internal:///./node_modules/@edx/frontend-platform/react/ErrorBoundary.js:104:5) at IntlProvider (webpack-internal:///./node_modules/react-intl/lib/src/components/provider.js:42:47) at AppProvider (webpack-internal:///./node_modules/@edx/frontend-platform/react/AppProvider.js:117:25)

I am NOT certain about the reason for this error, but I suspect it's probably connected to not defining any properties in the slots. Thus, making the plugin-slots library's implementation do something that React doesn't like.

I don't see this on the sandbox that we have setup so I am assuming it wouldn't be a big thing and it should be handled on the building step and is a problem for dev build.

farhaanbukhsh · 2025-10-14T09:27:53Z

@tecoholic @arbrandes @xitij2000 The sandbox https://axim-notification.do.opencraft.hosting/ has these changes so that you can test them. The configuration is passed through openedx/tutor-contrib-notifications#5

Signed-off-by: Farhaan Bukhsh <[email protected]>

tecoholic

@farhaanbukhsh 👍 Thank you for addressing all the comments. LGTM.

I tested this: Tested all the slots and verified that they are placed in the right places and function as intended.
I read through the code
I checked for accessibility issues
Includes documentation

tecoholic · 2025-10-15T11:08:39Z

src/studio-header/HeaderBody.tsx

    <Container
      size="xl"
-      className={classNames('px-2.5', containerClassName)}
+      className={classNames('px-0', containerClassName)}


Curious question: how does this padding affects the slot?

@tecoholic it gives breathing space to the content of the header else the header was looking very squishy

I'm unsure of this change. Perhaps it should be in a separate PR, it has nothing to do with the slots.

Okay let me undo this :)

brian-smith-tcril

I don't think we should add the slots that are currently in this PR.

I left some comments with more details, but overall:

I don't see how DesktopHeaderItemSlot and LearningHeaderItemSlot are adding anything that can't be accomplished with existing slots
MobileHeaderItemSlot and StudioHeaderItemSlot are adding new functionality, but in "serves one specific use case" ways. I left suggestions about ways to add the functionality in more versatile ways.

brian-smith-tcril · 2025-10-21T12:45:08Z

src/plugin-slots/DesktopHeaderItemSlot/README.md

@@ -0,0 +1,50 @@
+# Desktop Header Item Slot


My main question about this slot is just, "Is it needed?"

It's not clear to me what functionality is it providing that cannot be accomplished by following the "Add Custom Components before and after Menu" example for org.openedx.frontend.layout.header_desktop_secondary_menu.v1

I think you are right here, the use case of adding before and after makes this simpler. Thank you for introducing this to me :)

brian-smith-tcril · 2025-10-21T12:52:39Z

src/plugin-slots/LearningHeaderItemSlot/README.md

@@ -0,0 +1,51 @@
+# Learning Header Item Slot


Similar to my question about org.openedx.frontend.layout.desktop_header_item_slot.v1 - it's not clear to me what functionality this is providing that isn't available by using org.openedx.frontend.layout.header_learning_help.v1.

I realize the only example we have for the Learning Help Slot is fully replacing it, but we could definitely add a "keepDefault/insert before" example.

brian-smith-tcril · 2025-10-21T12:59:35Z

src/mobile-header/MobileHeader.jsx

      {userMenu.length > 0 || loggedOutItems.length > 0 ? (
        <div className="w-100 d-flex justify-content-end align-items-center">
          <Menu tag="nav" aria-label={intl.formatMessage(messages['header.label.secondary.nav'])} className="position-static">
+            <MobileHeaderItemSlot />


It seems odd to have this inside the Menu component. Does it not work when moved up one level?
I also think it might make more sense/provide more flexibility if we added a slot that wraps the entirety of the mobile user and logged out items menus.

We currently have org.openedx.frontend.layout.header_mobile_user_menu.v1 which wraps the user menu content, org.openedx.frontend.layout.header_mobile_logged_out_items.v1 which wraps the logged out items menu content, and org.openedx.frontend.layout.header_mobile_user_menu_trigger.v1 which wraps the content of the MenuTrigger button, but nothing that wraps it all at the top level.

If we had a slot that wrapped the entire thing, then we could use the "keepDefault/insert before" pattern for this.

brian-smith-tcril · 2025-10-21T13:21:52Z

src/plugin-slots/StudioHeaderItemSlot/README.md

@@ -0,0 +1,51 @@
+# Studio Header Item Slot


Considering the use case for this slot, I think it would make sense to instead create a slot that wraps the search button.

That would:

Allow plugin authors following the keepDefault pattern to either insert before, after, or both instead of only being able to insert before the search button

Allow plugin authors to completely replace the search button if desired

Effectively communicate what the slot is and where it lives.

openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels Oct 12, 2025

openedx-webhooks added this to Contributions Oct 12, 2025

github-project-automation bot moved this to Needs Triage in Contributions Oct 12, 2025

farhaanbukhsh added 3 commits October 12, 2025 16:42

feat: Adds notification tray slot

abae6d3

Signed-off-by: Farhaan Bukhsh <[email protected]>

feat: Add learning header iterm slot

ef5bc07

Signed-off-by: Farhaan Bukhsh <[email protected]>

feat: Add slots to authoring MFE header

0d9fd63

Signed-off-by: Farhaan Bukhsh <[email protected]>

farhaanbukhsh force-pushed the farhaan/refactoring-slots branch from f255ff6 to e60fac3 Compare October 12, 2025 11:13

farhaanbukhsh changed the title ~~Farhaan/refactoring slots~~ Adding new slots for Notification Tray integration Oct 12, 2025

This was referenced Oct 12, 2025

feat: Adds notification tray slot #638

Closed

Adding and upstreaming NotificationSlot openedx/frontend-plugin-notifications#50

Open

farhaanbukhsh requested review from arbrandes and xitij2000 October 12, 2025 15:41

tecoholic suggested changes Oct 13, 2025

View reviewed changes

farhaanbukhsh mentioned this pull request Oct 14, 2025

feat: Initial implementation openedx/tutor-contrib-notifications#3

Closed

farhaanbukhsh added 3 commits October 14, 2025 18:29

feat: Add Learner dashboard slot

77ec124

Signed-off-by: Farhaan Bukhsh <[email protected]>

feat: Add MobileHeaderItemSlot

610c663

Signed-off-by: Farhaan Bukhsh <[email protected]>

chore: Adds new slots the readme

ffa337b

Signed-off-by: Farhaan Bukhsh <[email protected]>

farhaanbukhsh force-pushed the farhaan/refactoring-slots branch from 31b5286 to ffa337b Compare October 14, 2025 12:59

farhaanbukhsh requested a review from tecoholic October 15, 2025 11:08

tecoholic approved these changes Oct 15, 2025

View reviewed changes

fixup! chore: Adds new slots the readme

ed08e48

xitij2000 approved these changes Oct 15, 2025

View reviewed changes

mphilbrick211 moved this from Needs Triage to In Eng Review in Contributions Oct 15, 2025

brian-smith-tcril reviewed Oct 21, 2025

View reviewed changes

Adding new slots for Notification Tray integration #644

Are you sure you want to change the base?

Adding new slots for Notification Tray integration #644

Conversation

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

Uh oh!

Uh oh!

openedx-webhooks commented Oct 12, 2025

Uh oh!

codecov bot commented Oct 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

tecoholic left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Missing priority in the widget definitions

JSX key spread warning

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!

farhaanbukhsh commented Oct 13, 2025

Missing priority in the widget definitions

JSX key spread warning

Uh oh!

farhaanbukhsh commented Oct 14, 2025

Uh oh!

tecoholic left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

farhaanbukhsh Oct 15, 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!

brian-smith-tcril left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

farhaanbukhsh 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!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

farhaanbukhsh commented Oct 12, 2025 •

edited

Loading

codecov bot commented Oct 12, 2025 •

edited

Loading

tecoholic left a comment •

edited

Loading

Missing `priority` in the `widget` definitions

JSX `key` spread warning

Missing `priority` in the `widget` definitions

JSX `key` spread warning

farhaanbukhsh Oct 15, 2025 •

edited

Loading

farhaanbukhsh Oct 22, 2025 •

edited

Loading