Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API prep for reconnection callback syncing indicator #2524

Merged
merged 6 commits into from
May 4, 2021

Conversation

marcaaron
Copy link
Contributor

@marcaaron marcaaron commented Apr 21, 2021

Details

Doing some prep work for E/E 159767

Fixed Issues (prep work does not fix)

https://github.com/Expensify/Expensify/issues/159767

Tests

  1. Inspect the Application storage in Chrome Dev Tools and filter for isLoadingAfterReconnect
  2. Turn off Wi-Fi and wait until indicator turns grey next to avatar
  3. Turn on Wi-Fi and verify that isLoadingAfterReconnect is set to true then eventually changes to false
2021-04-23_09-17-26.mp4

QA Steps

  1. Test for basic regressions around logging in/out, reports loading, etc

Tested On

  • Web
  • Mobile Web
  • Desktop
  • iOS
  • Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

@marcaaron marcaaron self-assigned this Apr 21, 2021
undo changes

nully

remove more unneeded changes
@marcaaron marcaaron force-pushed the marcaaron-reconnectionIndicator branch from 30767e6 to 8e308c9 Compare April 21, 2021 23:21
@marcaaron marcaaron marked this pull request as ready for review April 23, 2021 19:21
@marcaaron marcaaron requested a review from a team as a code owner April 23, 2021 19:21
@MelvinBot MelvinBot requested review from pecanoro and removed request for a team April 23, 2021 19:22
@marcaaron
Copy link
Contributor Author

Fixed conflicts on this one.

*/
function fetch() {
API.Get({
function fetchPersonalDetails() {
Copy link
Contributor

@pecanoro pecanoro May 4, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NAB: Why did you rename fetch? Since it's under PersonalDetails, it implies it's personal details what it's retrieving.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this is a personal preference to put in my personal details ? 😖

When we have a generic export like fetch() it encourages renaming imports and ultimately makes it hard to track down usages of things e.g. take several examples:

Here we can rename this to whatever and it makes finding things hell

import {fetch as fetchDetails} from './PersonalDetails';
import {fetch as fetchThePersonalDetails} from './PersonalDetails';
import * as PersonalDetails;
PersonalDetails.fetch();

Here there is no confusion and if we search for the name we'll always find and it's less likely someone will change the name to avoid a conflict with another generic fetch().

import * as PersonalDetails from './PersonalDetails';
PersonalDetails.fetchPersonalDetails();
import {fetchPersonalDetails} from './PersonalDetails';

Searching for fetchPersonalDetails in the latest case would bring up all usages.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha, it now makes sense!

@pecanoro pecanoro merged commit 9974e79 into main May 4, 2021
@pecanoro pecanoro deleted the marcaaron-reconnectionIndicator branch May 4, 2021 17:45
@OSBotify
Copy link
Contributor

OSBotify commented May 4, 2021

✋ 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
Copy link
Contributor

OSBotify commented May 4, 2021

🚀 Deployed to staging in version: 1.0.36-1🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented May 8, 2021

🚀 Deployed to production in version: 1.0.39-5🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants