-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Conversation
undo changes nully remove more unneeded changes
30767e6
to
8e308c9
Compare
Fixed conflicts on this one. |
*/ | ||
function fetch() { | ||
API.Get({ | ||
function fetchPersonalDetails() { |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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!
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging in version: 1.0.36-1🚀
|
🚀 Deployed to production in version: 1.0.39-5🚀
|
Details
Doing some prep work for E/E 159767
Fixed Issues (prep work does not fix)
https://github.com/Expensify/Expensify/issues/159767
Tests
isLoadingAfterReconnect
isLoadingAfterReconnect
is set totrue
then eventually changes tofalse
2021-04-23_09-17-26.mp4
QA Steps
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android