Resolved issue_Category - Parent category is disabled when selected by ijmalik · Pull Request #85448 · Expensify/App

ijmalik · 2026-03-16T18:05:09Z

Explanation of Change

Fixed Issues

$#85359, #85364,#85357,#82068
PROPOSAL:

Tests

Test Case 1: Category - Parent category is disabled when selected #85359
Precondition:Create both categories - Car and Car: Tesla
1.Go to workspace chat.
2.Create an expense with Tesla subcategory.
3.Open the expense.
4.Click Category.
5.On the search field, type Car.
6.Car will be enabled because Car is a valid category (there are Car and Car: Tesla categories).

Test Case 2: Search keeps parent and subcategories together #85364

Precondition:
Create both categories - D and D:E:F

1.Go to staging.new.expensify.com
2.Go to workspace chat.
3.Click + > Create expense > Manual.
4.Enter amount > Next.
5.Click Category.
6.Select D.
7.Click Category.
On the search field, type D.

Verify that Parent category (D) and subcategories (E and F) will be arranged together.

Test Case 3: Category - Category appears as disabled when the category is A: B: #85357

Precondition:

Create this category - A: B:

1.Go to staging.new.expensify.com
2.Go to workspace chat.
3.Click + > Create expense > Manual.
4.Enter amount > Next.
5.Click Category.
6.Expected Result:

Verify that B: will be enabled.

Test Case 4: Category starting with a colon #85361

Precondition: Create a category named :D in the workspace.

1.Go to staging.new.expensify.com
2.Go to workspace chat.
3.Click + → Create expense → Manual.
4.Enter amount → Next.
5.Click Category.
6.Expected Result:
The category :D appears as a top‑level item with no indentation (i.e., not shown as a subcategory).

Test Case 5: Selected field shows only leaf category

Precondition: Workspace has a category Parent:Child.

1.Go to workspace chat.
2.Create an expense and select the category Parent:Child.
3.After selection, observe the field that displays the chosen category (e.g., in the expense form).
4.Expected Result:
Only the leaf name Child is displayed, not the full path Parent:Child.

Verify that no errors appear in the JS console

Offline tests

Same as Tests

QA Steps

Same as Tests

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

melvin-bot · 2026-03-16T18:05:50Z

@youssef-lr 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]

ZhenjaHorbach · 2026-03-16T18:50:11Z

@@ -65,7 +65,10 @@ function getCategoryOptionTree(options: Record<string, Category> | Category[], i
            const isChild = array.length - 1 === index;
            const searchText = array.slice(0, index + 1).join(CONST.PARENT_CHILD_SEPARATOR);
            const selectedParentOption = !isChild && Object.values(selectedOptions).find((op) => op.name === searchText);
-            const isParentOptionDisabled = !selectedParentOption || !selectedParentOption.enabled || selectedParentOption.pendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE;
+            const optionParent = !isChild && Object.values(options).find((op) => op.name === searchText);


I'm a bit confused
We reverted the original PR
But where are the changes from the original PR?

Could you open a PR with the main changes from the reverted PR + with all regression fixes?

ZhenjaHorbach · 2026-03-16T19:21:11Z

Did you cover all these issues?

#85364
#85359
#85352

If yes
Please link these issues in the PR description
And add test cases for these issues in the description

And in addition, here we wait for the expected behavior

#85361
#85357

ijmalik · 2026-03-16T19:35:24Z

@ZhenjaHorbach #85359 is resolved, working on others.

codecov · 2026-03-16T19:37:30Z

Codecov Report

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

Files with missing lines	Coverage Δ
src/CONST/index.ts	`92.30% <ø> (ø)`
...c/components/ReportActionItem/MoneyRequestView.tsx	`74.65% <100.00%> (ø)`
...ents/TransactionItemRow/DataCells/CategoryCell.tsx	`100.00% <100.00%> (ø)`
src/libs/MergeTransactionUtils.ts	`78.78% <100.00%> (+0.18%)`	⬆️
...RequestConfirmationList/sections/CategoryField.tsx	`0.00% <0.00%> (ø)`
...equestReportView/MoneyRequestReportGroupHeader.tsx	`0.00% <0.00%> (ø)`
...m/TransactionPreview/TransactionPreviewContent.tsx	`80.15% <0.00%> (ø)`
...omponents/SelectionList/ListItem/SplitListItem.tsx	`0.00% <0.00%> (ø)`
src/libs/CategoryOptionListUtils.ts	`95.14% <96.55%> (+0.46%)`	⬆️
src/pages/iou/SplitExpenseEditPage.tsx	`0.00% <0.00%> (ø)`
... and 1 more
... and 10 files with indirect coverage changes

ZhenjaHorbach · 2026-03-18T10:08:20Z

@ijmalik
Any updates?

ijmalik · 2026-03-19T10:21:51Z

Hi @ZhenjaHorbach,

Thanks for checking! Here's the status of each issue:

✅ Resolved & Pushed

#85364 - Parent category separated from subcategories when searched – Fixed in latest commit
#85359 - Parent category disabled when selected – Fixed

⏳ Waiting on Design Decision

#85361 - Category field shows full path in composer – Confirmed same behavior as OldDot, awaiting final product/design decision

🚫 Not Related to This PR

#85352 - Long category names truncated – Separate UI issue, not caused by our changes

WIP

#85357 - Category appears disabled with trailing colon –. Currently working on it

I've updated the PR description with links to these issues and added test cases for the resolved ones. Let me know if you need anything else!

ZhenjaHorbach · 2026-03-19T10:23:42Z

Waiting on Design Decision

#85361 (comment) – Confirmed same behavior as OldDot, awaiting final product/design decision

I think we can leave the same behaviour as in OD

ijmalik · 2026-03-19T10:52:18Z

@ZhenjaHorbach

Observation:
I noticed an issue that appears to be unrelated to this PR, but wanted to bring it to your attention so it can be assigned to the right person.

Precondition:

Create a multi‑level category D:E:F (where E is a middle level, not a leaf).

Expected Behavior:
In the expense category picker, only leaf categories (like F) should be selectable. Middle levels (like E) should not be selectable.

Actual Result:
1- When clicking the circular radio button at the end of the row for category E, it becomes selected – which is incorrect. This should not be possible.

Note: Only the circular radio button is selectable; clicking anywhere else on the row (including the category name) does nothing.

Could you please help direct this issue to the appropriate person or PR author? It seems to have been introduced elsewhere.

Thanks!

cat-select-able.webm

ZhenjaHorbach · 2026-03-19T11:09:24Z

Oh
Good point
I will try to find somebody

ZhenjaHorbach · 2026-03-19T12:34:52Z

Created a bug for this issue
Thanks for noticing!

ijmalik · 2026-03-20T19:21:15Z

@ZhenjaHorbach

#85357 - Category appears disabled with trailing colon –. Resolved and pushed the commit

If you see any further potential edge cases I might have missed, Please let me know and I’ll address them promptly.

The PR description has been updated with links to the issue and testing steps.

Let me know if anything else is needed.

Thanks

ZhenjaHorbach · 2026-03-21T09:38:47Z

Lint and jest issues

ijmalik · 2026-03-21T13:15:25Z

@ZhenjaHorbach I'm working on resolving the lint and Jest issues – will push an update shortly.

ijmalik · 2026-03-22T18:32:22Z

@ZhenjaHorbach The lint and Jest issues have been resolved.

ZhenjaHorbach · 2026-03-24T12:52:27Z

I will recheck today!

youssef-lr · 2026-03-26T23:41:16Z

bump @ZhenjaHorbach

ZhenjaHorbach · 2026-03-27T09:14:38Z

I will check today!

ZhenjaHorbach · 2026-03-27T09:31:52Z

I'm not sure that is the right behaviour
I suppose we don't need to show parent categories for selected items

And how it looks on staging

ZhenjaHorbach · 2026-04-30T08:05:51Z

Sorry for the delay

@ijmalik
Could you fix the conflicts, please?

ijmalik · 2026-05-01T02:52:47Z

@ZhenjaHorbach – conflicts resolved and branch updated to latest main. Ready for review. Please let me know if anything else is needed.

ZhenjaHorbach · 2026-05-04T11:19:55Z

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

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

2026-05-04.14.17.48.mov

2026-05-04.14.22.52.mov

2026-05-04.14.24.14.mov

2026-05-04.14.25.32.mov

2026-05-04.14.28.44.mov

ZhenjaHorbach · 2026-05-04T12:46:49Z

Actually, I'm not sure about this behaviour
If I try to find a parent category, the parent and child categories are available
But if I try to find a child category, the parent category is not available

CC: @trjExpensify

2026-05-04.14.45.23.mov

trjExpensify · 2026-05-06T01:35:52Z

Classic isn't very sophisticated in this regard.

If the parent category is selectable it appears in search, if it's not selectable, it doesn't.
The search for the child category only returns the matching result.

It does run the risk of ending up in a scenario like the below if you have matching child category names:

2026-05-06_02-27-22.mp4

So I think showing the parent and child like you have in your video is an improvement for context in that case. But I think the logic for what you outlined should be based solely on whether that parent is selectable or not as a result of the config. I.e

Category A
Category A: Child 1
Category A: Child 2

^^ in this scenario Category A would have a radio button as it's independently selectable as a category.

Category A: Child 1
Category A: Child 2

^^ in this scenario Category A would not have a radio button as it's not independently selectable as a category.

ZhenjaHorbach · 2026-05-14T07:24:40Z

Classic isn't very sophisticated in this regard.

If the parent category is selectable it appears in search, if it's not selectable, it doesn't.

The search for the child category only returns the matching result.

It does run the risk of ending up in a scenario like the below if you have matching child category names:

2026-05-06_02-27-22.mp4
So I think showing the parent and child like you have in your video is an improvement for context in that case. But I think the logic for what you outlined should be based solely on whether that parent is selectable or not as a result of the config. I.e

Category A
Category A: Child 1
Category A: Child 2

^^ in this scenario Category A would have a radio button as it's independently selectable as a category.

Category A: Child 1
Category A: Child 2

^^ in this scenario Category A would not have a radio button as it's not independently selectable as a category.

@ijmalik
Can you check this comment?

ijmalik · 2026-05-14T13:58:24Z

Classic isn't very sophisticated in this regard.

If the parent category is selectable it appears in search, if it's not selectable, it doesn't.

The search for the child category only returns the matching result.

It does run the risk of ending up in a scenario like the below if you have matching child category names:
2026-05-06_02-27-22.mp4
So I think showing the parent and child like you have in your video is an improvement for context in that case. But I think the logic for what you outlined should be based solely on whether that parent is selectable or not as a result of the config. I.e

Category A
Category A: Child 1
Category A: Child 2

^^ in this scenario Category A would have a radio button as it's independently selectable as a category.

Category A: Child 1
Category A: Child 2

^^ in this scenario Category A would not have a radio button as it's not independently selectable as a category.

@ijmalik Can you check this comment?

@ZhenjaHorbach

Yes, it is working in the same manner.

Kindly check below video link:
https://drive.google.com/file/d/1OeA2VSvy_nILqXxHVi-eN-v4OGZQ_u6j/view?usp=sharing

ijmalik · 2026-05-15T02:27:53Z

@ZhenjaHorbach – To add more detail to my previous reply:

Scenario1:
Category A
Category A: Child 1
Category A: Child 2

Scenario2:
Category A2: Child 1
Category A2: Child 2

This PR already implements the behavior trjExpensify described:

Scenario 1 (Category A exists as a standalone category) → Category A is selectable.

Scenario 2 (Category A2 exists only as a parent label, not as a standalone category) → Category A2 is not selectable.

Please see the video for confirmation: Demo Video

Let me know if any further adjustments are needed.

CC: trjExpensify

ZhenjaHorbach · 2026-05-15T11:59:25Z

I will complete reviewing today or on the weekend

ZhenjaHorbach · 2026-05-18T16:06:17Z

Okay then
Overall, changes work well
Will recheck one thing and will approve tomorrow morning!

OSBotify · 2026-05-19T18:40:13Z

✋ 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-05-19T18:45:49Z

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

github-actions · 2026-05-19T18:50:49Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-053ca5e-67d807d-e7c58144190c74ebfc5bb08c48ae74efc6031500/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-053ca5e-67d807d-579bf194f739142a02204956a688f335eea9ba3c/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-05-19T22:07:28Z

🚀 Deployed to staging by https://github.com/yuwenmemon in version: 9.3.78-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-05-19T22:09:16Z

I reviewed the changes in this PR against all category-related help site articles under App/docs/articles:

new-expensify/workspaces/Create-expense-categories.md
expensify-classic/workspaces/Create-categories.md
new-expensify/workspaces/Require-tags-and-categories-for-expenses.md
new-expensify/insights/View-the-Top-Categories-report.md
expensify-classic/workspaces/Set-up-category-automation.md

No help site changes are required.

This PR is a bug fix for internal category separator parsing and subcategory display logic (disabled states, search grouping, leaf-name display). No user-facing workflows, settings labels, navigation paths, or documented behavior changed — only internal code handling was corrected.

lanitochka17 · 2026-05-19T22:38:47Z

Deploy Blocker ##91133 was identified to be related to this PR.

ijmalik · 2026-05-20T03:27:46Z

I’ve reviewed the behavior in OldDot/Classic for a category named : and found the following:

A category : can be created.
In the category dropdown, it appears as an empty line (no visible text).
Clicking that empty line does not fill the category field – the field remains empty.
The category : is effectively not selectable.

This means that OldDot does not support selecting a colon-only category either – it simply shows a blank entry that does nothing.

Our PR’s behavior (the colon category not appearing in the list) is visually different but functionally identical: the category : cannot be selected or used in an expense. The PR does not introduce a regression in terms of selectability – it was already impossible in OldDot.

If the expectation is to fully support : as a selectable category, that would require changes beyond the scope of this PR (it would need frontend work to treat alone colon as a valid category name). I recommend handling that as a separate feature request.

For now, the PR remains consistent with the legacy behavior (no selection possible). Please let me know if you’d still like me to adjust the PR, or if we can close this deploy blocker.

Please see OldDot Demo Video

CC: @yuwenmemon, @ZhenjaHorbach

OSBotify · 2026-05-21T21:25:35Z

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.78-1 🚀

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

ijmalik requested review from a team as code owners March 16, 2026 18:05

melvin-bot Bot assigned ijmalik Mar 16, 2026

melvin-bot Bot requested review from heyjennahay and youssef-lr and removed request for a team March 16, 2026 18:05

ijmalik mentioned this pull request Mar 16, 2026

[Due for payment 2026-05-28] Category - Parent category is disabled when selected #85359

Closed

7 tasks

ZhenjaHorbach reviewed Mar 16, 2026

View reviewed changes

ijmalik force-pushed the 85359-PR branch from 82ef94a to 6915cf0 Compare March 20, 2026 18:58

ijmalik force-pushed the 85359-PR branch 2 times, most recently from 0254fd4 to 5b1c6e1 Compare March 22, 2026 18:15

Merge branch 'main' into 85359-PR

e7fd08a

Merge branch 'main' into 85359-PR

9d54bce

Merge branch 'main' into 85359-PR

1188322

Merge branch 'main' into 85359-PR

35699e3

ZhenjaHorbach approved these changes May 19, 2026

View reviewed changes

melvin-bot Bot requested a review from yuwenmemon May 19, 2026 12:34

yuwenmemon approved these changes May 19, 2026

View reviewed changes

yuwenmemon merged commit 053ca5e into Expensify:main May 19, 2026
38 checks passed

OSBotify mentioned this pull request May 19, 2026

Deploy Checklist: New Expensify 2026-05-19 #91122

Closed

39 tasks

applause-bot Bot mentioned this pull request May 19, 2026

[Due for payment 2026-06-12] [$250] Expense - Colon symbol category cannot be selected as category #91133

Open

7 tasks

This was referenced May 19, 2026

Category - Parent category is separated from subcategories when searched #85364

Closed

Category - Category appears as disabled when the category is A: B: #85357

Closed

Conversation

ijmalik commented Mar 16, 2026 • 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!

melvin-bot Bot commented Mar 16, 2026

Uh oh!

ZhenjaHorbach Mar 16, 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!

ZhenjaHorbach commented Mar 16, 2026

Uh oh!

ijmalik commented Mar 16, 2026

Uh oh!

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

Uh oh!

Codecov Report

Uh oh!

ZhenjaHorbach commented Mar 18, 2026

Uh oh!

ijmalik commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ZhenjaHorbach commented Mar 19, 2026

Uh oh!

ijmalik commented Mar 19, 2026

Uh oh!

ZhenjaHorbach commented Mar 19, 2026

Uh oh!

ZhenjaHorbach commented Mar 19, 2026

Uh oh!

ijmalik commented Mar 20, 2026

Uh oh!

ZhenjaHorbach commented Mar 21, 2026

Uh oh!

ijmalik commented Mar 21, 2026

Uh oh!

ijmalik commented Mar 22, 2026

Uh oh!

ZhenjaHorbach commented Mar 24, 2026

Uh oh!

youssef-lr commented Mar 26, 2026

Uh oh!

ZhenjaHorbach commented Mar 27, 2026

Uh oh!

ZhenjaHorbach commented Mar 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ZhenjaHorbach commented Apr 30, 2026

Uh oh!

ijmalik commented May 1, 2026

Uh oh!

ZhenjaHorbach commented May 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

ZhenjaHorbach commented May 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

trjExpensify commented May 6, 2026

Uh oh!

ZhenjaHorbach commented May 14, 2026

Uh oh!

ijmalik commented May 14, 2026

Uh oh!

ijmalik commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ZhenjaHorbach commented May 15, 2026

Uh oh!

ZhenjaHorbach commented May 18, 2026

Uh oh!

ijmalik commented Mar 16, 2026 •

edited

Loading

ZhenjaHorbach Mar 16, 2026 •

edited

Loading

codecov Bot commented Mar 16, 2026 •

edited by github-actions Bot

Loading

ijmalik commented Mar 19, 2026 •

edited

Loading

ZhenjaHorbach commented Mar 27, 2026 •

edited

Loading

ZhenjaHorbach commented May 4, 2026 •

edited

Loading

ZhenjaHorbach commented May 4, 2026 •

edited

Loading

ijmalik commented May 15, 2026 •

edited

Loading

ijmalik commented May 20, 2026 •

edited

Loading