[NO QA] [Odometer] Build Odometer expense image capture flow by jakubkalinski0 · Pull Request #79576 · Expensify/App

jakubkalinski0 · 2026-01-14T14:26:43Z

Explanation of Change

This PR implements the next part of the Odometer feature, aligned with Phase 1 tasks 1.D (capture start/end images) and 1.E (discard/clear on tab switch). This PR focuses on the web implementation of the image capture flow with image preview, native implementation and mobile web implementation to follow

1.D (Capture start/end images) - added a dedicated ODOMETER_IMAGE screen and route. We intentionally did not reuse IOURequestStepScan because that screen includes receipt‑specific behaviors (SmartScan, location prompts, receipt state logic). On web we follow an established patter of keeping a minimal upload UI that uses the existing drag‑and‑drop + file picker tooling on web.
- Route + navigator entry:

DISTANCE_REQUEST_CREATE_TAB_ODOMETER: {
    route: 'distance-odometer',
    getRoute: (action: IOUAction, iouType: IOUType, transactionID: string, reportID: string, backToReport?: string) =>
        `${action as string}/${iouType as string}/start/${transactionID}/${reportID}/distance-new${backToReport ? `/${backToReport}` : ''}/distance-odometer` as const,
},
ODOMETER_IMAGE: {
    route: 'odometer-image/:transactionID/:readingType',
    getRoute: (transactionID: string, readingType: 'start' | 'end') => `odometer-image/${transactionID}/${readingType}` as const,
},

[SCREENS.MONEY_REQUEST.STEP_DISTANCE_GPS]: () => require<ReactComponentModule>('../../../../pages/iou/request/step/IOURequestStepDistanceGPS').default,
[SCREENS.MONEY_REQUEST.STEP_DISTANCE_ODOMETER]: () => require<ReactComponentModule>('../../../../pages/iou/request/step/IOURequestStepDistanceOdometer').default,
[SCREENS.MONEY_REQUEST.ODOMETER_IMAGE]: () => require<ReactComponentModule>('../../../../pages/iou/request/step/IOURequestStepOdometerImage').default,

Web upload UI (localized title/message + drag‑drop + picker):

function IOURequestStepOdometerImage({
    route: {
        params: {transactionID, readingType},
    },
}: IOURequestStepOdometerImageProps) {
    const title = readingType === 'start' ? translate('distance.odometer.startTitle') : translate('distance.odometer.endTitle');
    const message = readingType === 'start' ? translate('distance.odometer.startMessageWeb') : translate('distance.odometer.endMessageWeb');
    const icon = readingType === 'start' ? lazyIcons.OdometerStart : lazyIcons.OdometerEnd;
    ...
    const handleImageSelected = useCallback(
        (file: FileObject) => {
            setMoneyRequestOdometerImage(transactionID, readingType, file as File, isTransactionDraft);
            navigateBack();
        },
        [transactionID, readingType, isTransactionDraft, navigateBack],
    );
    ...
}

1.D (Inline thumbnails + entry point) - the odometer step renders image thumbnails next to the reading inputs so users can add/replace each image in context. We store the images on transaction.comment (odometerStartImage / odometerEndImage) rather than creating a separate draft store in Phase 1. This is intentional: draft storage is reserved for Phase 2 “Save for later”, while the transaction comment keeps the data tied to the in‑progress expense and survives navigation/confirmation without extra persistence logic.

<PressableWithFeedback
    accessible={false}
    accessibilityRole="button"
    onPress={() => handleCaptureImage('start')}
    style={[
        StyleUtils.getWidthAndHeightStyle(variables.inputHeight, variables.inputHeight),
        StyleUtils.getBorderRadiusStyle(variables.componentBorderRadiusMedium),
        styles.overflowHidden,
        StyleUtils.getBackgroundColorStyle(theme.border),
    ]}
>
    <ReceiptImage
        source={startImageSource ?? ''}
        shouldUseThumbnailImage
        thumbnailContainerStyles={styles.bgTransparent}
        isAuthTokenRequired
        fallbackIcon={GalleryPlus}
        ...
    />
</PressableWithFeedback>

function setMoneyRequestOdometerImage(transactionID: string, imageType: 'start' | 'end', file: File | string, isDraft: boolean) {
    const imageKey = imageType === 'start' ? 'odometerStartImage' : 'odometerEndImage';
    Onyx.merge(`${isDraft ? ONYXKEYS.COLLECTION.TRANSACTION_DRAFT : ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`, {
        comment: {
            [imageKey]: file,
        },
    });
}

1.E (Discard/clear on tab switch) - the doc explicitly states that switching away from Odometer should clear unsaved inputs. We do this by listening to the selected tab key and resetting the local state only when the user leaves the odometer tab. This avoids false resets while typing and matches the behavior of the other distance tabs.

const [selectedTab, selectedTabResult] = useOnyx(`${ONYXKEYS.COLLECTION.SELECTED_TAB}${CONST.TAB.DISTANCE_REQUEST_TYPE}`, {canBeMissing: true});
const isLoadingSelectedTab = isLoadingOnyxValue(selectedTabResult);
...
useEffect(() => {
    if (isLoadingSelectedTab) {
        return;
    }
    const prevSelectedTab = prevSelectedTabRef.current;
    if (prevSelectedTab === CONST.TAB_REQUEST.DISTANCE_ODOMETER && selectedTab !== CONST.TAB_REQUEST.DISTANCE_ODOMETER) {
        setStartReading('');
        setEndReading('');
        ...
    }
    prevSelectedTabRef.current = selectedTab;
}, [selectedTab, isLoadingSelectedTab]);

1.E (Discard Changes modal) - unsaved changes now include both readings and images so users don’t lose photos by accidentally backing out.

<DiscardChangesConfirmation
    isEnabled={shouldEnableDiscardConfirmation}
    getHasUnsavedChanges={() => {
        const hasReadingChanges = startReadingRef.current !== initialStartReadingRef.current || endReadingRef.current !== initialEndReadingRef.current;
        const hasImageChanges =
            transaction?.comment?.odometerStartImage !== initialStartImageRef.current || transaction?.comment?.odometerEndImage !== initialEndImageRef.current;
        return hasReadingChanges || hasImageChanges;
    }}
/>

Fixed Issues

$ #77266
PROPOSAL: N/A

Tests

Go to FAB and press Track distance
Select the Odometer tab and verify the start/end reading inputs and image placeholders render.
Enter a start reading, then an end reading, and verify the total distance updates.
Tap the start image placeholder, choose a file, and verify you return to the odometer step with a start thumbnail shown
Tap the end image placeholder, choose a file, and verify you return with an end thumbnail shown
Open each image picker again and switch the image, verify the thumbnail updates accordingly
Switch to another distance tab and then back to Odometer - verify the fields are reset
Continue to the confirmation step, then go back to edit the distance step and verify the entered readings and thumbnails persist
On web, drag-and-drop an image onto the odometer image screen - verify it uploads and shows the correct thumbnail
With only the image chosen try pressing < button or outside of the RHP and verify if the DiscardChangesConfirmation is shown

Verify that no errors appear in the JS console

Offline tests

Turn off network.
Repeat all steps from the Tests section and verify the thumbnails still appear

QA Steps

Same as Tests

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

MacOS: Chrome / Safari

Online:

online.mov

Offline:

offline.mov

…se_image_capture_flow

codecov · 2026-01-14T14:44:39Z

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/CONST/index.ts	`87.39% <100.00%> (ø)`
src/SCREENS.ts	`100.00% <ø> (ø)`
...rc/components/Icon/chunks/expensify-icons.chunk.ts	`0.00% <ø> (ø)`
src/libs/DebugUtils.ts	`68.63% <ø> (ø)`
src/libs/Navigation/linkingConfig/config.ts	`75.00% <ø> (ø)`
...iou/request/step/withFullTransactionOrNotFound.tsx	`88.23% <ø> (ø)`
src/ROUTES.ts	`13.10% <0.00%> (-0.02%)`	⬇️
src/components/DropZone/DropZoneUI.tsx	`0.00% <0.00%> (ø)`
...gation/AppNavigator/ModalStackNavigators/index.tsx	`7.70% <0.00%> (-0.02%)`	⬇️
src/libs/actions/IOU/index.ts	`72.07% <0.00%> (-0.02%)`	⬇️
... and 2 more
... and 166 files with indirect coverage changes

melvin-bot · 2026-01-14T15:21:46Z

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

Look at the code and make sure there are no malicious changes.
Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

jakubkalinski0 · 2026-01-14T15:26:43Z

This version is working, but the code needs to be cleaned up and some minor things have to be fixed. I am done for today but will work on this tomorrow with the aim of finishing it for initial review 🤞

…se_image_capture_flow

jakubkalinski0 · 2026-01-21T17:45:29Z

So it took a few days for tomorrow to finally come 😅

…se_image_capture_flow

DylanDylann · 2026-02-04T06:41:22Z

@jakubkalinski0 I left some comments above. Could you take a look when you're available?

…se_image_capture_flow

jakubkalinski0 · 2026-02-04T16:27:01Z

@jakubkalinski0 Looks like we haven't covered the mobile web platform in this PR, right?

@DylanDylann Yeah, I wanted to split it into smaller PRs to allow for more thorough review. I also plan to do both native and mobile web separately as well as I assume native itself will be big enough on itself

jakubkalinski0 · 2026-02-04T17:01:20Z

@jakubkalinski0 Why don't we show the Discard Changes modal when switching to another distance request type?

cc @shawnborton Do you think we should show the Discard Changes modal when switching to another distance request type?

When it comes to the topic of not showing Discard Changes modal when switching to another distance request type you can actually read more about it in the discussion in the docs. It was decided back then to simply match the behavior of manual and map, but I personally agree that it would make sense to show this modal when image is given.

I agree with Jules that we should revisit this discussion in the issue taking care of this modal

jakubkalinski0 · 2026-02-04T22:08:16Z

For now, can you just reuse this one? The styling should look how it does for our standard receipt drag and drop flow.

@shawnborton does it look good enough for now?

Screen.Recording.2026-02-04.at.23.05.52.mov

Julesssss · 2026-02-04T23:38:46Z

@DylanDylann please review when you're available, we're getting close now 🤞

For any further UI issues I'll create issues separately as the feature is not visible to users.

jakubkalinski0 · 2026-02-05T00:34:18Z

I will also fix the performance issue in a second. I want to make sure that revoking the blob url on image page works properly as it's being a bit of a headache at the moment

Julesssss · 2026-02-05T00:47:20Z

I want to make sure that revoking the blob url on image page works properly as it's being a bit of a headache at the moment

It sounds like a good candidate for separating out from this PR perhaps?

jakubkalinski0 · 2026-02-05T01:27:57Z

@Julesssss Actually I think that it pretty much works as it should now. We now reuse existing blob URLs (file.uri - set in the dropHandler) instead of creating new ones on every render, and we explicitly revoke URLs when the image changes or the screen unmounts. For drag‑and‑drop, the blob URLs are tracked and cleared on the next drop, on unmount if selection isn’t confirmed, and the IOURequestStepDistanceOdometer screen revokes its own blob URLs on unmount or when the image changes.

If you have any comments (or you @DylanDylann), please let me know and if there are any more problems or doubts then we can revisit this in a separate issue.

Screen.Recording.2026-02-05.at.02.03.34.mov

src/pages/iou/request/DistanceRequestStartPage.tsx

DylanDylann · 2026-02-05T05:33:31Z

src/pages/iou/request/step/IOURequestStepDistanceOdometer.tsx

+    // Reset component state when switching away from the odometer tab
    useEffect(() => {
-        if (!isFocused) {
+        if (isLoadingSelectedTab) {


@jakubkalinski0 Kindly bump

shawnborton · 2026-02-05T05:51:34Z

Yup, looking much better - thanks!

DylanDylann · 2026-02-05T06:30:41Z

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-05.at.12.38.39.mov

DylanDylann · 2026-02-05T06:31:37Z

The rest looks fine to me

github-actions · 2026-02-05T17:19:55Z

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

github-actions · 2026-02-05T17:24:53Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-6e22ce7-7c484bfa75aca9143dcab985ac8f4fa82c0f1d96/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-6e22ce7-e473b320748dc17935b4cc8b32405437d14bd196/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-02-05T20:46:24Z

🚀 Deployed to staging by https://github.com/Julesssss in version: 9.3.13-1 🚀

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

OSBotify · 2026-02-05T21:46:50Z

🚀 Deployed to staging by https://github.com/Julesssss in version: 9.3.15-0 🚀

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

Added image displays for odometer

5c66404

melvin-bot bot assigned jakubkalinski0 Jan 14, 2026

jakubkalinski0 added 2 commits January 14, 2026 15:34

Prettier run

a412406

Merge branch 'main' into jakubkalinski0/Odometer_Build_Odometer_expen…

d09e290

…se_image_capture_flow

jakubkalinski0 mentioned this pull request Jan 14, 2026

[Odometer] Build Odometer expense image capture flow #77266

Open

Added IOURequestStepOdometerImage screen for web

d79e152

Prettier run

d86f3c6

jakubkalinski0 added 2 commits January 21, 2026 15:55

Merge branch 'main' into jakubkalinski0/Odometer_Build_Odometer_expen…

487d51c

…se_image_capture_flow

Merge branch 'main' into jakubkalinski0/Odometer_Build_Odometer_expen…

39f1b00

…se_image_capture_flow

jakubkalinski0 added 12 commits January 21, 2026 20:28

Adjust style of ImageOdometer screen

879e455

Merge branch 'main' into jakubkalinski0/Odometer_Build_Odometer_expen…

fc8c1dc

…se_image_capture_flow

Updated icons for odometer image capture

322da5a

Merge branch 'main' into jakubkalinski0/Odometer_Build_Odometer_expen…

1f65491

…se_image_capture_flow

Merge branch 'main' into jakubkalinski0/Odometer_Build_Odometer_expen…

b7f533e

…se_image_capture_flow

Styling of odometer image and code cleanup

a583eee

prettier run

3f285e0

Remove odometer mobile translations

ac70488

Code cleanup

6096440

prettier run

f41a9d2

Merge branch 'main' into jakubkalinski0/Odometer_Build_Odometer_expen…

57c268c

…se_image_capture_flow

Added spanish translation

9c4ec73

This comment has been minimized.

Sign in to view

jakubkalinski0 added 4 commits January 30, 2026 00:55

Added missing translations

75bfc69

Merge branch 'main' into jakubkalinski0/Odometer_Build_Odometer_expen…

a0d22cf

…se_image_capture_flow

Fix merge conflict

f35ca71

Adjusted icon of the odometer image dropzone

e2769a4

Merge branch 'main' into jakubkalinski0/Odometer_Build_Odometer_expen…

230bb91

…se_image_capture_flow

jakubkalinski0 dismissed Julesssss’s stale review via 230bb91 February 4, 2026 15:14

Fix conflict

e277b70

Added sentryLabels to odometer page

ecca2b4

jakubkalinski0 added 2 commits February 4, 2026 23:30

Adjusted DropZone icons for odometer

36ac49e

prettier run

07cd6e8

revoke blob urls on unmount in odometer

7dc6a71

jakubkalinski0 added 3 commits February 5, 2026 03:00

Added OdomtereImageType to consts

f920698

Added action and ioutype to odometer image route

7c858cf

fix eslint

30762e7

DylanDylann reviewed Feb 5, 2026

View reviewed changes

Hide odometer tab behind a flag

d9f95a1

Julesssss approved these changes Feb 5, 2026

View reviewed changes

Julesssss merged commit 6e22ce7 into Expensify:main Feb 5, 2026
32 checks passed

OSBotify mentioned this pull request Feb 5, 2026

Deploy Checklist: New Expensify 2026-02-05 #81590

Open

Conversation

jakubkalinski0 commented Jan 14, 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!

codecov bot commented Jan 14, 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!

melvin-bot bot commented Jan 14, 2026

Uh oh!

jakubkalinski0 commented Jan 14, 2026

Uh oh!

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

Uh oh!

Uh oh!

This comment has been minimized.

DylanDylann commented Feb 4, 2026

Uh oh!

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

Uh oh!

Uh oh!

jakubkalinski0 commented Feb 4, 2026

Uh oh!

jakubkalinski0 commented Feb 4, 2026

Uh oh!

Julesssss commented Feb 4, 2026

Uh oh!

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

Uh oh!

Uh oh!

Julesssss commented Feb 5, 2026

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

DylanDylann Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

shawnborton commented Feb 5, 2026

Uh oh!

DylanDylann commented Feb 5, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

DylanDylann commented Feb 5, 2026

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026

Uh oh!

github-actions bot commented Feb 5, 2026

Uh oh!

OSBotify commented Feb 5, 2026

Uh oh!

OSBotify commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

jakubkalinski0 commented Jan 14, 2026 •

edited

Loading

codecov bot commented Jan 14, 2026 •

edited by github-actions bot

Loading

jakubkalinski0 commented Jan 21, 2026 •

edited

Loading

jakubkalinski0 commented Feb 4, 2026 •

edited

Loading

jakubkalinski0 commented Feb 5, 2026 •

edited

Loading

jakubkalinski0 commented Feb 5, 2026 •

edited

Loading