-
Notifications
You must be signed in to change notification settings - Fork 35
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
Bugfix/issue7 #11
Bugfix/issue7 #11
Conversation
8d13692
to
79c3188
Compare
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.
- Love the direction on this demo so far
- README LGTM
- Can we change the current output in https://www.dropbox.com/s/njov9dyw1ekw98y/issue7-overview.PNG?dl=0 to say "effective network connection" instead of "Network Connection"?
import './App.css'; | ||
import IFixitSearch from './containers/IFixitSearch'; |
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.
Can we change this to iFixitSearch?
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'm afraid it looks like it's sort of rules in React component naming.
https://www.dropbox.com/s/7kc6g9x0lm9wf49/2.PNG?dl=0
Let me try to find warning ignore comment for this.
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.
Ah. Not a huge deal then :)
</a> | ||
</header> | ||
<div className='App-content'> | ||
<IFixitSearch /> |
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.
Similar comment to earlier (iFixitSearch)
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.
The same reason as above.
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. Similar to above, I'd say we can skip this change then.
Yes, I did so. |
|
||
import './search-bar.css'; | ||
|
||
const SearchBar = ({ search }) => { |
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.
Do we currently throttle how often we query the API? We probably want to avoid doing this onChange for every keystroke, right?
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.
Now, we just call API once clicking on search icon, not calling API in every onChange event.
In every onChange event, we just update the input value.
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.
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.
Thanks, let me check and update the codes.
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.
Ah, okay - so testing out https://anton-karlovskiy-network-aware-data-fetching-for-glitch.glitch.me/ I see that you need to tap on the magnifying glass in order to search (vs it searching on key-press). Rather than change this, maybe we can add the ability to search if you hit the ENTER key too?
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.
No problem. :)
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 added Enter key feature. You can check it on glitch version as I updated it as well.
.then(response => response.json()) | ||
.then(response => { | ||
setLoading(false); | ||
console.log('ray : response => ', response); |
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.
Could we drop the ray
logs?
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.
Ah yes.
Milica advised me to include glitch in PR. |
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.
LGTM
Following is thumbnails in different resolution:
https://d3nevzfk7ii3be.cloudfront.net/igi/sX5iMoIvYMbCvHoF.thumbnail
https://d3nevzfk7ii3be.cloudfront.net/igi/sX5iMoIvYMbCvHoF.huge