Storybook run without error #51530

Anaslancer · 2024-10-26T19:22:41Z

@ishpaul777

Details

I've added the initiaizations for the React Navigation when isJestEnv is false in this file.

Fixed Issues

$ #51108
PROPOSAL: #51108 (comment)

Tests

Open the Command Prompt or Terminal
Go to the folder that includes the code base.
Run this command, npm run storybook
After build, Open the Web browser and type the link occured by npm run storybook.
Confirm if the storybook run without error.

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

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 / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
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 verified the translation was requested/reviewed 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 correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- 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.js 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 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
  - 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(themeColors.componentBG)
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 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.
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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

(cherry picked from commit 904e715)

…angeToBumpApp [NO QA] Minor formatting alignment (cherry picked from commit 3a3f182) (CP triggered by Julesssss)

melvin-bot · 2024-10-26T19:22:46Z

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

github-actions · 2024-10-26T19:22:55Z

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

ishpaul777 · 2024-10-26T19:25:04Z

@Anaslancer your commit is unsigned, PR also includes unnecessary changes, please fix this

Anaslancer · 2024-10-26T19:56:05Z

I have read the CLA Document and I hereby sign the CLA

Anaslancer · 2024-10-26T20:11:43Z

@ishpaul777 Thank you for your quick response. And should I revert all build versions?

ishpaul777 · 2024-10-27T20:00:08Z

yes.. only relevant changes are in __mocks__/@react-navigation/native/index.ts

Anaslancer · 2024-10-28T11:21:31Z

Hi @ishpaul777 Should I check these checkboxes? Thanks

ishpaul777 · 2024-10-28T13:55:12Z

__mocks__/@react-navigation/native/index.ts

 const useNavigation = () => ({
    ...realReactNavigation.useNavigation,


Suggested change

const useNavigation = () => ({

...realReactNavigation.useNavigation,

const realOrMockedUseNavigation = isJestEnv ? realReactNavigation.useNavigation : {};

const useNavigation = () => ({

...realOrMockedUseNavigation,

ishpaul777 · 2024-10-28T14:01:49Z

Hi @ishpaul777 Should I check these checkboxes? Thanks

yes you can check the checkbox that not relevant to PR

Anaslancer · 2024-10-28T15:16:28Z

@ishpaul777 How can I accept this?

ishpaul777 · 2024-10-28T15:18:30Z

No further action required from your side, i'll re review in few hours

ishpaul777 · 2024-10-28T19:37:30Z

Form story is still crashing

i think we also have to mock useRoute and useFocusEffect

+ const useRoute = isJestEnv ? realReactNavigation.useRoute : () => ({params: {}});
+ const useFocusEffect = isJestEnv ? realReactNavigation.useFocusEffect : (callback: () => void) => callback();

export {
    // Overriden modules
    useIsFocused,
    useTheme,
    useNavigation,
    triggerTransitionEnd,
+  useRoute,
+  useFocusEffect,
//.  rest of exports

Anaslancer · 2024-10-28T20:15:15Z

@ishpaul777 Thank you for your help. You are genius.

ishpaul777 · 2024-10-28T21:01:03Z

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 tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- 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 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- 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.js 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.
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.2024-10-29.at.2.18.22.AM.mov

OSBotify · 2024-10-28T21:44:21Z

✋ 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 · 2024-10-29T09:45:37Z

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

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

ishpaul777 · 2024-10-29T22:31:38Z

This is a [NO QA] pr

github-actions · 2024-10-31T11:18:58Z

🚀 Deployed to production by https://github.com/Beamanator in version: 9.0.55-10 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	skipped 🚫
🍎🔄 iOS HybridApp 🍎🔄	skipped 🚫

OSBotify and others added 3 commits October 25, 2024 10:44

Update version to 9.0.54-1

b020eee

(cherry picked from commit 904e715)

Merge pull request Expensify#51455 from Expensify/jules-minorReadmeCh…

080b4a9

…angeToBumpApp [NO QA] Minor formatting alignment (cherry picked from commit 3a3f182) (CP triggered by Julesssss)

initialize when isJestEnv is false

e822a3d

Anaslancer requested a review from a team as a code owner October 26, 2024 19:22

melvin-bot bot requested review from ishpaul777 and removed request for a team October 26, 2024 19:22

CLABotify added a commit to Expensify/CLA that referenced this pull request Oct 26, 2024

@Anaslancer has signed the CLA in Expensify/App#51530

3dc66de

Update README.md

c7df9a7

Anaslancer added 6 commits October 28, 2024 07:04

Update build.gradle

7a67207

Update Info.plist

658f468

Update Info.plist

df248a1

Update Info.plist

c4a5b61

Update package.json

a724319

Update package-lock.json

862c2ea

Anaslancer marked this pull request as draft October 28, 2024 11:18

Anaslancer marked this pull request as ready for review October 28, 2024 11:19

ishpaul777 reviewed Oct 28, 2024

View reviewed changes

Update index.ts

3e766cc

Anaslancer requested a review from ishpaul777 October 28, 2024 15:10

Anaslancer marked this pull request as draft October 28, 2024 15:13

Anaslancer marked this pull request as ready for review October 28, 2024 15:14

Update index.ts

06eab28

ishpaul777 approved these changes Oct 28, 2024

View reviewed changes

melvin-bot bot requested a review from yuwenmemon October 28, 2024 21:02

yuwenmemon approved these changes Oct 28, 2024

View reviewed changes

yuwenmemon merged commit da2e668 into Expensify:main Oct 28, 2024
17 checks passed

github-actions bot mentioned this pull request Oct 29, 2024

Deploy Checklist: New Expensify 2024-10-29 #51635

Closed

65 tasks

melvin-bot bot mentioned this pull request Oct 31, 2024

[HOLD for payment 2024-11-07] Unable to run storybook locally #51108

Closed

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Storybook run without error #51530

Storybook run without error #51530

Anaslancer commented Oct 26, 2024 •

edited

Loading

melvin-bot bot commented Oct 26, 2024

github-actions bot commented Oct 26, 2024 •

edited

Loading

ishpaul777 commented Oct 26, 2024

Anaslancer commented Oct 26, 2024

Anaslancer commented Oct 26, 2024

ishpaul777 commented Oct 27, 2024

Anaslancer commented Oct 28, 2024

ishpaul777 Oct 28, 2024

Anaslancer Oct 28, 2024

ishpaul777 commented Oct 28, 2024

Anaslancer commented Oct 28, 2024

ishpaul777 commented Oct 28, 2024

ishpaul777 commented Oct 28, 2024

Anaslancer commented Oct 28, 2024

ishpaul777 commented Oct 28, 2024

OSBotify commented Oct 28, 2024

github-actions bot commented Oct 29, 2024

ishpaul777 commented Oct 29, 2024

github-actions bot commented Oct 31, 2024

		const useNavigation = () => ({
		...realReactNavigation.useNavigation,

Storybook run without error #51530

Storybook run without error #51530

Conversation

Anaslancer commented Oct 26, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Oct 26, 2024

github-actions bot commented Oct 26, 2024 • edited Loading

ishpaul777 commented Oct 26, 2024

Anaslancer commented Oct 26, 2024

Anaslancer commented Oct 26, 2024

ishpaul777 commented Oct 27, 2024

Anaslancer commented Oct 28, 2024

ishpaul777 Oct 28, 2024

Choose a reason for hiding this comment

Anaslancer Oct 28, 2024

Choose a reason for hiding this comment

ishpaul777 commented Oct 28, 2024

Anaslancer commented Oct 28, 2024

ishpaul777 commented Oct 28, 2024

ishpaul777 commented Oct 28, 2024

Anaslancer commented Oct 28, 2024

ishpaul777 commented Oct 28, 2024

Reviewer Checklist

Screenshots/Videos

OSBotify commented Oct 28, 2024

github-actions bot commented Oct 29, 2024

ishpaul777 commented Oct 29, 2024

github-actions bot commented Oct 31, 2024

Anaslancer commented Oct 26, 2024 •

edited

Loading

github-actions bot commented Oct 26, 2024 •

edited

Loading