feat: Add thumbnail support for receipts and improve image handling by kubabutkiewicz · Pull Request #84919 · Expensify/App

kubabutkiewicz · 2026-03-11T17:58:30Z

Explanation of Change

Fixed Issues

$#83503
PROPOSAL:

Tests

Go to create expense flow
Select scan
Take a photo
Go to confirmation screen
Verify that thumbnail is showing properly

Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as above

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I followed proper code patterns (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
  - If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- 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 followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
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
I verified that if a function's arguments changed that all usages have also been updated correctly
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 new assets were added or existing ones were modified, I verified that:
- The assets are optimized and compressed (for SVG files, run npm run compress-svg)
- The assets load correctly across all supported platforms.
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.
I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

melvin-bot · 2026-03-11T17:58:39Z

@brunovjk 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]

src/pages/iou/request/step/IOURequestStepScan/cropImageToAspectRatio.ts

marcaaron · 2026-03-12T00:54:17Z

src/pages/iou/request/step/IOURequestStepScan/cropImageToAspectRatio.ts

+ * Used on native to avoid decoding the full 12MP camera photo on the confirmation page.
+ */
+function generateThumbnail(sourceUri: string, maxWidth = 512): Promise<string | undefined> {
+    return ImageManipulator.manipulate(sourceUri)


We definitely should check this on Android and iOS both. I think I saw on my crappy Galaxy S8 that the image preview on confirmation page takes about 1 second to load without any resizing.

But, also I think we can control the overall file size by tweaking the vision camera settings e.g. if we use takeSnapshot() instead of takePhoto() then maybe this thumbnail generation is not needed? Or the tradeoff is less? Hard to say! Hacking over here.

…to pregenerate-thumbnails-for-the-confirm-screen

codecov · 2026-03-12T10:15:48Z

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/libs/DebugUtils.ts	`68.60% <ø> (ø)`
src/libs/actions/IOU/Receipt.ts	`65.93% <100.00%> (+0.76%)`	⬆️
src/libs/fileDownload/FileUtils.ts	`32.29% <ø> (ø)`
...u/request/step/IOURequestStepScan/index.native.tsx	`68.88% <ø> (+0.75%)`	⬆️
.../components/MoneyRequestConfirmationListFooter.tsx	`56.16% <83.33%> (-22.88%)`	⬇️
src/libs/ReceiptUtils.ts	`75.00% <0.00%> (ø)`
.../step/IOURequestStepScan/cropImageToAspectRatio.ts	`44.44% <12.50%> (-9.13%)`	⬇️
src/hooks/useLocalReceiptThumbnail.ts	`38.88% <38.88%> (ø)`
... and 9 files with indirect coverage changes

…ath. This change improves performance by decoupling thumbnail generation from the main receipt processing flow, ensuring that the UI remains responsive during photo capture. Updated logic for setting receipt files and handling editing state accordingly.

src/pages/iou/request/step/IOURequestStepScan/cropImageToAspectRatio.ts

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6c74437146

ℹ️ 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".

src/pages/iou/request/step/IOURequestStepScan/index.native.tsx

src/libs/actions/IOU/index.ts

trjExpensify · 2026-03-13T13:46:41Z

PR doesn’t need product input as a performance PR. Unassigning and unsubscribing myself.

…to pregenerate-thumbnails-for-the-confirm-screen

brunovjk · 2026-03-18T15:35:40Z

@kubabutkiewicz can you resolve the comments about inconsistency? Do you think we could add some unit tests here? Thanks.

…to pregenerate-thumbnails-for-the-confirm-screen

kubabutkiewicz · 2026-04-02T08:49:20Z

@brunovjk @Julesssss
I think this is fine but let me know? The goal of this PR is to introduce the pregeneration of the thumbnail right after you took a pic and not block the transition to the confirmation while the generation of the thumbnail is happening so there could be a time when you land on the confirmation and the thumbnail is not ready yet

kubabutkiewicz · 2026-04-02T08:55:07Z

Maybe we can create some better UX here, like instead of showing blank preview, show some blured template image and replace it with the generated thumbnail when its ready

Julesssss · 2026-04-02T17:30:49Z

Maybe we can create some better UX here, like instead of showing blank preview, show some blured template image and replace it with the generated thumbnail when its ready

Yeah even though the perf improvement is good, the flash isn't great. Perhaps a slight fade in animation or placeholder.

…to pregenerate-thumbnails-for-the-confirm-screen

…mation screen. Update `useLocalReceiptThumbnail` to manage thumbnail caching and references, preventing source swaps. Adjust `MoneyRequestConfirmationListFooter` to utilize cached thumbnails effectively. Ensure seamless integration in `IOURequestStepScan` for enhanced user experience.

kubabutkiewicz · 2026-04-04T19:01:39Z

@brunovjk @Julesssss I investigated it a bit and I found the solution which wont cause flickering nor the need of introduction of loader/animation

brunovjk · 2026-04-06T14:33:02Z

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

84919_android_native.mov

Android: mWeb Chrome

84919_web_native.mov

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

N/A

brunovjk · 2026-04-06T14:34:47Z

@Julesssss can you help me test it on iOS? I don't have a physical iOS device, and I couldn't unlock the camera in the simulator. Thanks a lot.

github-actions · 2026-04-06T22:19:50Z

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

github-actions · 2026-04-06T22:40:11Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-8e8bcf0-85a3263-887a08a0c7acbd1a48bb2aaaec666b0dac6b9043/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-8e8bcf0-85a3263-c5c1420ceb58517dcc958cb0c91e0563f757c779/index.html

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

👀 View the workflow run that generated this build 👀

Julesssss · 2026-04-06T22:46:41Z

@Julesssss can you help me test it on iOS? I don't have a physical iOS device, and I couldn't unlock the camera in the simulator. Thanks a lot.

Yeah I can do this tomorrow

Julesssss · 2026-04-06T22:55:29Z

Ah @kubabutkiewicz could you merge main tomorrow and resolve conflicts too, thanks

…to pregenerate-thumbnails-for-the-confirm-screen

kubabutkiewicz · 2026-04-07T07:23:14Z

@Julesssss on it!

…width to 256px for faster decoding. Implement prefetching of thumbnails to eliminate latency during display. Update IOURequestStepScan to handle thumbnail generation and navigation more efficiently.

…to pregenerate-thumbnails-for-the-confirm-screen

Julesssss · 2026-04-07T18:31:30Z

@Julesssss on it!

Oh no another conflict, sorry!

…to pregenerate-thumbnails-for-the-confirm-screen

OSBotify · 2026-04-07T20:37:16Z

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

Julesssss · 2026-04-07T20:45:27Z

iOS tested well for me. I noticed one issue that I raised as a separate bug.

github-actions · 2026-04-07T21:00:45Z

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

github-actions · 2026-04-07T21:05:49Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-a8b0925-bfd3c12-bc1fe72c9d87d62b9ae385bb6d233fc595bea81d/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-a8b0925-bfd3c12-e62ab1b61a405317c2c12e00fcddb5834647a607/index.html

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

👀 View the workflow run that generated this build 👀

feat: Add thumbnail support for receipts and improve image handling

d6fa27a

kubabutkiewicz requested review from a team as code owners March 11, 2026 17:58

melvin-bot bot assigned kubabutkiewicz Mar 11, 2026

melvin-bot bot requested review from brunovjk and trjExpensify and removed request for a team March 11, 2026 17:58

melvin-bot bot removed the request for review from a team March 11, 2026 17:58

kubabutkiewicz marked this pull request as draft March 11, 2026 17:59

kubabutkiewicz mentioned this pull request Mar 11, 2026

[Metrics] ManualShutterToConfirmation - Optimize "Confirm details" page rendering after receipt capture #83503

Open

github-actions bot reviewed Mar 11, 2026

View reviewed changes

src/pages/iou/request/step/IOURequestStepScan/cropImageToAspectRatio.ts Outdated Show resolved Hide resolved

github-actions bot reviewed Mar 11, 2026

View reviewed changes

src/pages/iou/request/step/IOURequestStepScan/cropImageToAspectRatio.ts Outdated Show resolved Hide resolved

marcaaron reviewed Mar 12, 2026

View reviewed changes

marcaaron requested review from Julesssss and marcaaron March 12, 2026 00:54

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

35be2b4

…to pregenerate-thumbnails-for-the-confirm-screen

kubabutkiewicz added 2 commits March 12, 2026 18:49

resolve lint issue

6c74437

kubabutkiewicz marked this pull request as ready for review March 12, 2026 17:51

github-actions bot reviewed Mar 12, 2026

View reviewed changes

src/pages/iou/request/step/IOURequestStepScan/cropImageToAspectRatio.ts Outdated Show resolved Hide resolved

github-actions bot reviewed Mar 12, 2026

View reviewed changes

src/pages/iou/request/step/IOURequestStepScan/cropImageToAspectRatio.ts Show resolved Hide resolved

chatgpt-codex-connector bot reviewed Mar 12, 2026

View reviewed changes

src/pages/iou/request/step/IOURequestStepScan/index.native.tsx Outdated Show resolved Hide resolved

src/libs/actions/IOU/index.ts Outdated Show resolved Hide resolved

kubabutkiewicz marked this pull request as draft March 12, 2026 18:09

trjExpensify removed their request for review March 13, 2026 13:46

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

90397b1

…to pregenerate-thumbnails-for-the-confirm-screen

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

af737d4

…to pregenerate-thumbnails-for-the-confirm-screen

This comment has been minimized.

Sign in to view

kubabutkiewicz added 2 commits April 4, 2026 11:51

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

cbfb4f1

…to pregenerate-thumbnails-for-the-confirm-screen

brunovjk approved these changes Apr 6, 2026

View reviewed changes

melvin-bot bot requested a review from Julesssss April 6, 2026 14:33

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

f24b70f

…to pregenerate-thumbnails-for-the-confirm-screen

kubabutkiewicz added 3 commits April 7, 2026 11:07

Enhance thumbnail generation for confirmation screen by reducing max …

5beb1fa

…width to 256px for faster decoding. Implement prefetching of thumbnails to eliminate latency during display. Update IOURequestStepScan to handle thumbnail generation and navigation more efficiently.

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

6acd919

…to pregenerate-thumbnails-for-the-confirm-screen

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

3b1ef08

…to pregenerate-thumbnails-for-the-confirm-screen

kubabutkiewicz added 2 commits April 7, 2026 22:01

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

49d3c60

…to pregenerate-thumbnails-for-the-confirm-screen

fix lint

512c481

Julesssss approved these changes Apr 7, 2026

View reviewed changes

Julesssss merged commit a8b0925 into Expensify:main Apr 7, 2026
31 checks passed

Julesssss mentioned this pull request Apr 7, 2026

Receipt thumbnail on confirmation page not updated after replacing image #87284

Open

Conversation

kubabutkiewicz commented Mar 11, 2026 • edited by Julesssss 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 11, 2026

Uh oh!

Uh oh!

Uh oh!

marcaaron Mar 12, 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!

codecov bot commented Mar 12, 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!

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

trjExpensify commented Mar 13, 2026

Uh oh!

brunovjk commented Mar 18, 2026

Uh oh!

This comment has been minimized.

kubabutkiewicz commented Apr 2, 2026

Uh oh!

kubabutkiewicz commented Apr 2, 2026

Uh oh!

Julesssss commented Apr 2, 2026

Uh oh!

kubabutkiewicz commented Apr 4, 2026

Uh oh!

brunovjk commented Apr 6, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

brunovjk commented Apr 6, 2026

Uh oh!

github-actions bot commented Apr 6, 2026

Uh oh!

github-actions bot commented Apr 6, 2026

Uh oh!

Julesssss commented Apr 6, 2026

Uh oh!

Julesssss commented Apr 6, 2026

Uh oh!

kubabutkiewicz commented Apr 7, 2026

Uh oh!

Julesssss commented Apr 7, 2026

Uh oh!

Uh oh!

OSBotify commented Apr 7, 2026

Uh oh!

Julesssss commented Apr 7, 2026

Uh oh!

github-actions bot commented Apr 7, 2026

Uh oh!

github-actions bot commented Apr 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

kubabutkiewicz commented Mar 11, 2026 •

edited by Julesssss

Loading

marcaaron Mar 12, 2026 •

edited

Loading

codecov bot commented Mar 12, 2026 •

edited by github-actions bot

Loading