Remove `Onyx.connect()` for the key: `ONYXKEYS.COLLECTION.REPORT` in `OptionsListUtils.ts` by abzokhattab · Pull Request #78645 · Expensify/App

abzokhattab · 2025-12-31T16:42:53Z

Explanation of Change

Fixed Issues

$ #66378
PROPOSAL:

Tests

Prerequisite: Log into an account that has existing chats and expense reports.

Open the app and wait for the LHN to fully load.
Verify the LHN shows your chats with correct preview text under each chat name.
Create a new expense by tapping the + (Plus) button → Submit Expense → complete the expense flow.
Navigate back to the LHN and verify the new expense report appears with the correct last message preview.
Open that expense report, add a comment, then go back to the LHN.
Confirm the LHN preview text updates to show your new comment.
Use the Search at the top to search for a chat by name.
Verify search results display correctly with proper preview text.

Offline tests

Same as tests

QA Steps

Same as tests

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2026-01-16.at.15.43.55.mov

Android: mWeb Chrome

Screen.Recording.2026-01-16.at.15.48.09.mov

iOS: Native

Screen.Recording.2026-01-16.at.15.45.31.mov

iOS: mWeb Safari

Screen.Recording.2026-01-16.at.15.46.35.mov

MacOS: Chrome / Safari

Screen.Recording.2026-01-16.at.15.41.17.mov

…libs/OptionsListUtils.ts

codecov · 2025-12-31T16:52:02Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/components/AvatarCropModal/AvatarCropModal.tsx	`0.00% <ø> (ø)`
src/components/HeaderWithBackButton/index.tsx	`91.56% <ø> (ø)`
src/components/LHNOptionsList/LHNOptionsList.tsx	`83.87% <100.00%> (ø)`
src/components/LHNOptionsList/OptionRowLHNData.tsx	`87.50% <100.00%> (+0.54%)`	⬆️
src/components/Lightbox/index.tsx	`65.38% <ø> (ø)`
src/components/OptionListContextProvider.tsx	`86.02% <100.00%> (+1.18%)`	⬆️
src/components/PDFThumbnail/index.native.tsx	`16.66% <ø> (ø)`
...c/components/Search/SearchFiltersChatsSelector.tsx	`0.00% <ø> (ø)`
...onents/TransactionItemRow/ReceiptPreview/index.tsx	`0.00% <ø> (ø)`
src/libs/SidebarUtils.ts	`78.15% <ø> (ø)`
... and 8 more
... and 16 files with indirect coverage changes

melvin-bot · 2025-12-31T16:57:58Z

@alitoshmatov Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

…rom-optionslistutils.ts

alitoshmatov · 2026-01-05T20:53:40Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

report-android.mov

Android: mWeb Chrome

iOS: HybridApp

report-ios.mp4

iOS: mWeb Safari

MacOS: Chrome / Safari

report-web.mov

danieldoglas · 2026-01-06T18:11:40Z

@abzokhattab please fill the checklist

abzokhattab · 2026-01-06T18:16:36Z

yes in my list @danieldoglas sorry for the confusion.

…rom-optionslistutils.ts

abzokhattab · 2026-01-16T14:50:38Z

The PR is ready @alitoshmatov please take alook

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dabb99f408

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

…olution

…ptionslistutils.ts

alitoshmatov

Changes look good to me!

DylanDylann · 2026-01-19T03:36:23Z

+            const report = getReportOrDraftReport(reportID);
+            const chatReport = getReportOrDraftReport(report?.chatReportID);


@abzokhattab @alitoshmatov Why do we use getReportOrDraftReport? This function will be removed soon

I notice you are introducing many new usages of getReportOrDraftReport function

if u look closer, its used inside the Onyx.connect there is no way to get the report data inside the Onyx.connect other than getReportOrDraftReport

it will be all removed when this connect is removed

For this case, are we moving Onyx.connect from here to another file (not remove them)? 😄 I think we should hold off until we remove Onyx.connect for ONYXKEYS.COLLECTION.REPORT_ACTIONS. I'd prefer to keep it separated and avoid using Onyx.connect across files

danieldoglas · 2026-01-21T23:17:15Z

please fix the conflicts and I'll review/merge

DylanDylann · 2026-01-22T06:38:29Z

@@ -2021,12 +2026,12 @@ function prepareReportOptionsForDisplay(options: Array<SearchOption<Report>>, co

        let isOptionUnread = option.isUnread;
        if (shouldUnreadBeBold) {
-            const chatReport = allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${report.chatReportID}`];
+            const chatReport = getReportOrDraftReport(report.chatReportID);


@abzokhattab How about this? And other usage places of getReportOrDraftReport

Please check this warning: https://expensify.slack.com/archives/C02NK2DQWUX/p1759913248186279

cc @alitoshmatov

…rom-optionslistutils.ts

DylanDylann · 2026-01-26T14:10:00Z

@abzokhattab Could you consider splitting this into a separate PR? The code changes are getting quite large

tgolen · 2026-02-20T18:41:51Z

+    const userToInviteReportID = availableOptions?.userToInvite?.isPolicyExpenseChat ? availableOptions.userToInvite.reportID : undefined;
+    const [userToInviteExpenseReport] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT}${getNonEmptyStringOnyxID(userToInviteReportID)}`, {canBeMissing: true});
+    const [userToInviteChatReport] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT}${getNonEmptyStringOnyxID(userToInviteExpenseReport?.chatReportID)}`, {canBeMissing: true});


I see this duplicated a few times. Can you write a custom hook for it instead?

Good point, I agree we should create a hook to deduplicate the code

changed here 8837797

DylanDylann · 2026-02-23T06:52:45Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8837797203

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-02-23T07:07:41Z

+ */
+export default function useUserToInviteReports(userToInvite: SearchOptionData | null | undefined) {
+    const userToInviteReportID = userToInvite?.isPolicyExpenseChat ? userToInvite.reportID : undefined;
+    const [userToInviteExpenseReport] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT}${getNonEmptyStringOnyxID(userToInviteReportID)}`, {canBeMissing: true});


Read draft reports when resolving policy expense invitees

This hook now resolves policy expense chats only from ONYXKEYS.COLLECTION.REPORT, but this flow previously relied on getReportOrDraftReport() semantics that also include reportDraft_ entries. If the invite target is still optimistic/draft-only, userToInviteExpenseReport stays undefined, and downstream selectors pass incomplete data into getPolicyExpenseReportOption(...), which can render a broken/blank workspace option and incorrect participant metadata.

Useful? React with 👍 / 👎.

DylanDylann · 2026-02-23T07:16:21Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Screen.Recording.2026-02-23.at.14.06.33.mov

DylanDylann · 2026-02-23T07:16:47Z

@abzokhattab A few minor comments. Please ping me for approval after you address them all.

tgolen

This PR picked up quite a few conflicts.

…d chatReport to deps

…rom-optionslistutils.ts

tgolen · 2026-02-24T18:19:21Z

@abzokhattab Please don't ever force-push to your branch once people have begun to review it.

abzokhattab · 2026-02-24T18:20:54Z

Yes sorry i had those commits unverified so i had to repush

OSBotify · 2026-02-24T18:31:09Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2026-02-24T19:02:34Z

🚧 @tgolen has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-02-24T19:10:23Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #78645.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-2b7d723-7d3026d-adb53180ebf0a31057edb6211e7737874ad31b70/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-2b7d723-7d3026d-a1e8ff9fd28a618c0cd4aa9fbfc640046936f0b1/index.html

Web 🕸️
https://78645.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-02-25T18:22:45Z

🚀 Deployed to staging by https://github.com/tgolen in version: 9.3.26-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

OSBotify · 2026-02-27T14:54:18Z

🚀 Deployed to production by https://github.com/puneetlath in version: 9.3.26-8 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Remove Onyx.connect() for the key: ONYXKEYS.COLLECTION.REPORT in src/…

07f1d81

…libs/OptionsListUtils.ts

melvin-bot Bot assigned abzokhattab Dec 31, 2025

abzokhattab marked this pull request as ready for review December 31, 2025 16:57

abzokhattab requested review from a team as code owners December 31, 2025 16:57

melvin-bot Bot requested review from alitoshmatov and removed request for a team December 31, 2025 16:57

Merge remote-tracking branch 'origin/main' into Remove-onyx-connect-f…

1bac4b4

…rom-optionslistutils.ts

abzokhattab marked this pull request as draft January 6, 2026 18:16

abzokhattab added 2 commits January 16, 2026 11:49

Merge remote-tracking branch 'origin/main' into Remove-onyx-connect-f…

af1499f

…rom-optionslistutils.ts

fixing eslint warning

687ab58

abzokhattab marked this pull request as ready for review January 16, 2026 14:50

chatgpt-codex-connector Bot reviewed Jan 16, 2026

View reviewed changes

Comment thread src/libs/OptionsListUtils/index.ts Outdated

abzokhattab added 4 commits January 16, 2026 16:10

fix: pass reports collection to computeReportName for proper name res…

aefc340

…olution

minor ts fix

5cc558b

minor fix

b7fd95c

Merge remote-tracking branch 'origin' into Remove-onyx-connect-from-o…

03d2a20

…ptionslistutils.ts

alitoshmatov approved these changes Jan 18, 2026

View reviewed changes

melvin-bot Bot requested a review from danieldoglas January 18, 2026 23:53

DylanDylann reviewed Jan 19, 2026

View reviewed changes

DylanDylann reviewed Jan 22, 2026

View reviewed changes

Merge remote-tracking branch 'origin/main' into Remove-onyx-connect-f…

dee323b

…rom-optionslistutils.ts

abzokhattab requested a review from DylanDylann February 20, 2026 17:42

tgolen requested changes Feb 20, 2026

View reviewed changes

Extract useUserToInviteReports hook to deduplicate chatReport lookups

9930f02

abzokhattab requested a review from tgolen February 20, 2026 18:57

DylanDylann reviewed Feb 23, 2026

View reviewed changes

Comment thread src/pages/iou/request/MoneyRequestAttendeeSelector.tsx Outdated

Comment thread src/hooks/useUserToInviteReports.ts Outdated

chatgpt-codex-connector Bot reviewed Feb 23, 2026

View reviewed changes

tgolen previously approved these changes Feb 23, 2026

View reviewed changes

abzokhattab dismissed tgolen’s stale review via 74fde28 February 24, 2026 00:05

abzokhattab added 2 commits February 24, 2026 01:10

Address review comments: fix relative import, use ordered options, ad…

452ca95

…d chatReport to deps

Merge remote-tracking branch 'origin/main' into Remove-onyx-connect-f…

964ab04

…rom-optionslistutils.ts

abzokhattab force-pushed the Remove-onyx-connect-from-optionslistutils.ts branch 2 times, most recently from f7b4bdb to 964ab04 Compare February 24, 2026 00:15

abzokhattab added 2 commits February 24, 2026 01:33

fixing ts

eb615f3

fixing prettier

3e21c2e

abzokhattab requested review from DylanDylann and tgolen February 24, 2026 01:13

DylanDylann approved these changes Feb 24, 2026

View reviewed changes

tgolen approved these changes Feb 24, 2026

View reviewed changes

tgolen merged commit 2b7d723 into Expensify:main Feb 24, 2026
30 checks passed

OSBotify mentioned this pull request Feb 25, 2026

Deploy Checklist: New Expensify 2026-02-25 #83466

Closed

		const report = getReportOrDraftReport(reportID);
		const chatReport = getReportOrDraftReport(report?.chatReportID);

Uh oh!

Conversation

abzokhattab commented Dec 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov Bot commented Dec 31, 2025 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

melvin-bot Bot commented Dec 31, 2025

Uh oh!

alitoshmatov commented Jan 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

danieldoglas commented Jan 6, 2026

Uh oh!

abzokhattab commented Jan 6, 2026

Uh oh!

abzokhattab commented Jan 16, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

alitoshmatov left a comment

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!

DylanDylann Jan 22, 2026 • 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!

danieldoglas commented Jan 21, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

DylanDylann commented Jan 26, 2026

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!

DylanDylann commented Feb 23, 2026

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

DylanDylann commented Feb 23, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

DylanDylann commented Feb 23, 2026

Uh oh!

tgolen left a comment

abzokhattab commented Dec 31, 2025 •

edited

Loading

codecov Bot commented Dec 31, 2025 •

edited by github-actions Bot

Loading

alitoshmatov commented Jan 5, 2026 •

edited

Loading

DylanDylann Jan 22, 2026 •

edited

Loading