[No QA] Migrate static styles to use StyleSheet.create by staszekscp · Pull Request #70261 · Expensify/App

staszekscp · 2025-09-10T10:58:51Z

Explanation of Change

First phase of the styles optimisation. In this PR I split the styles object into smaller, separate ones:

staticStyles - style objects that can be wrapped by StyleSheet.create
dynamicStyles - style functions that return a specific style object (can't be wrapped by StyleSheet.create)
customPickerStyles - specific styles that are passed to react-native-picker-select
nestedStyles - style objects that cannot be wrapped by StyleSheet.create, because the style definition is not on the top level of the object. -> temporary solution that I'd like to fix in one of the follow-ups.

The introduction of StaticStyles and DynamicStyles is necessary for the smooth transition to StyleSheet.create, since it doesn't accept functions as key values.

Fixed Issues

$ #70099
PROPOSAL: https://swmansion.slack.com/archives/C08CZDJFJ77/p1756884100187419

Tests

Theoretically there should be no changes in the way the app works and displays content

Verify that no errors appear in the JS console

Offline tests

QA Steps

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2025-09-12.at.10.44.47.mov

Android: mWeb Chrome

Screen.Recording.2025-09-12.at.11.36.58.mov

iOS: Native

Screen.Recording.2025-09-12.at.09.59.32.mov

iOS: mWeb Safari

Screen.Recording.2025-09-12.at.10.01.14.mov

MacOS: Chrome / Safari

Screen.Recording.2025-09-12.at.11.34.35.mov

MacOS: Desktop

Screen.Recording.2025-09-12.at.11.28.33.mov

melvin-bot · 2025-09-15T05:43:03Z

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

staszekscp · 2025-09-15T05:45:11Z

Since the PR restructures one of files that is modified the most, I'm going to resolve conflicts after the review

adamgrzybowski

🎸

jayeshmangwani · 2025-09-16T11:15:16Z

+            },
+        }) satisfies CustomPickerStyle,
+});
+// Styles that don't satify the StyleSheet.create typing, because they are not defined on the top level of the object


spellcheck is failing for this

jayeshmangwani · 2025-09-16T13:01:31Z

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

Android: HybridApp

Android.mov

Android: mWeb Chrome

mweb-chrome.mov

iOS: HybridApp

iOS.mov

iOS: mWeb Safari

mweb-safari.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

jayeshmangwani

LGTM 🚀

Co-authored-by: Jayesh Mangwani <35371050+jayeshmangwani@users.noreply.github.com>

jayeshmangwani · 2025-09-16T13:23:19Z

@adamgrzybowski Sorry, the spelling in my comment was also wrong 😢 , I should have used the word satisfy.

adamgrzybowski · 2025-09-16T13:37:24Z

@jayeshmangwani, not a problem 😄 now it should be fixed for good 🤞

mountiny

Thank you!

OSBotify · 2025-09-17T18:24:54Z

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

OSBotify · 2025-09-19T22:52:51Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.2.16-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

OSBotify · 2025-09-23T19:34:55Z

🚀 Deployed to production by https://github.com/roryabraham in version: 9.2.16-14 🚀

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

Migrate static styles to use StyleSheet.create

881decf

melvin-bot Bot assigned staszekscp Sep 10, 2025

staszekscp added 3 commits September 11, 2025 12:38

Add dynamicStyles

37ac91d

Identify TypeScript issues

c60b764

Fix TypeScript by creating nestedStyles

e8f9cdb

staszekscp changed the title ~~Migrate static styles to use StyleSheet.create~~ [No QA] Migrate static styles to use StyleSheet.create Sep 12, 2025

staszekscp marked this pull request as ready for review September 15, 2025 05:42

staszekscp requested review from a team as code owners September 15, 2025 05:42

melvin-bot Bot requested a review from jayeshmangwani September 15, 2025 05:43

melvin-bot Bot removed the request for review from a team September 15, 2025 05:43

Modify STYLING.md to explain the change

8af2b53

adamgrzybowski approved these changes Sep 15, 2025

View reviewed changes

Merge branch 'main' into perf/migration-to-stylesheet

a467200

jayeshmangwani reviewed Sep 16, 2025

View reviewed changes

Comment thread src/styles/index.ts Outdated

jayeshmangwani approved these changes Sep 16, 2025

View reviewed changes

melvin-bot Bot requested a review from mountiny September 16, 2025 13:02

Update src/styles/index.ts

1ec988c

Co-authored-by: Jayesh Mangwani <35371050+jayeshmangwani@users.noreply.github.com>

fix typo

bf559d6

mountiny approved these changes Sep 17, 2025

View reviewed changes

mountiny merged commit 54e50da into Expensify:main Sep 17, 2025
19 checks passed

OSBotify mentioned this pull request Sep 19, 2025

Deploy Checklist: New Expensify 2025-09-19 #70900

Closed

neil-marcellini mentioned this pull request Sep 22, 2025

[Due for payment 2025-10-21] [$250] Expense - Amount input page resets to 0.00 after returning from confirm page twice #70941

Closed

16 tasks

staszekscp mentioned this pull request Sep 24, 2025

OLD [No QA] Revert Revert "Migrate static styles to use StyleSheet.create" #71163

Closed

51 tasks

jayeshmangwani mentioned this pull request Sep 24, 2025

[No QA] Move static values from dynamicStyles #70986

Merged

54 tasks

staszekscp mentioned this pull request Sep 24, 2025

Migrate static styles to use StyleSheet.create #71168

Merged

49 tasks

Navigation Menu

[No QA] Migrate static styles to use StyleSheet.create - #70261

[No QA] Migrate static styles to use StyleSheet.create#70261
mountiny merged 8 commits into
Expensify:mainfrom
software-mansion-labs:perf/migration-to-stylesheet

staszekscp commented Sep 10, 2025 •

edited

Loading

Uh oh!

melvin-bot Bot commented Sep 15, 2025

Uh oh!

staszekscp commented Sep 15, 2025

Uh oh!

adamgrzybowski left a comment

Uh oh!

jayeshmangwani Sep 16, 2025

Uh oh!

Uh oh!

jayeshmangwani commented Sep 16, 2025

Uh oh!

jayeshmangwani left a comment

Uh oh!

jayeshmangwani commented Sep 16, 2025

Uh oh!

adamgrzybowski commented Sep 16, 2025 •

edited

Loading

Uh oh!

mountiny left a comment

Uh oh!

Uh oh!

OSBotify commented Sep 17, 2025

Uh oh!

OSBotify commented Sep 19, 2025

Uh oh!

OSBotify commented Sep 23, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

staszekscp commented Sep 10, 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!

melvin-bot Bot commented Sep 15, 2025

Uh oh!

staszekscp commented Sep 15, 2025

Uh oh!

adamgrzybowski left a comment

Choose a reason for hiding this comment

Uh oh!

jayeshmangwani Sep 16, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

jayeshmangwani commented Sep 16, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

jayeshmangwani left a comment

Choose a reason for hiding this comment

Uh oh!

jayeshmangwani commented Sep 16, 2025

Uh oh!

adamgrzybowski commented Sep 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Sep 17, 2025

Uh oh!

OSBotify commented Sep 19, 2025

Uh oh!

OSBotify commented Sep 23, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

staszekscp commented Sep 10, 2025 •

edited

Loading

adamgrzybowski commented Sep 16, 2025 •

edited

Loading