-
Notifications
You must be signed in to change notification settings - Fork 165
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
cleanup and minor changes #101
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
src/App.js
Outdated
@@ -14,7 +14,7 @@ const App = () => { | |||
}; | |||
|
|||
return ( | |||
<> | |||
<React.Fragment> | |||
<Header onCategoryChange={handleCategoryChange} /> |
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 see why you asked about categories in the contributor's JSON. Good catch, as this callback function was from the template of the starter open-source project used to get this project off the ground and the JSON was organized differently then. In this case, we would not need this callback function since there is no category and changes taking place. And I agree with your proposed change.
@@ -14,7 +14,7 @@ const App = () => { | |||
}; | |||
|
|||
return ( | |||
<> | |||
<React.Fragment> | |||
<Header onCategoryChange={handleCategoryChange} /> | |||
<div className="flex justify-content-center" style={{ marginTop: "50px", padding: '50px' }}> |
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.
Nice good catch again, as I have just looked and ran on my local dev server, and it functions normally with <div className="flex justify-content-center" >
with your other proposed change on App.js l.21: there is margin and padding added on l.19 already —> can be removed (not changed)
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.
Wow! Thank you for taking the time to fix the naming of the classes, as this is a better naming convention now.
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.
Brilliant! I didn't even consider the ...
for the languages that go from right to left. That is a great detail you have highlighted and added. @sherikovic. It took me a little bit to realize why you were moving the ...
until I realized the language is written in the other language😅
I ran a search, and other languages that are right to left are:
- Aramaic
- Azeri
- Dhivehi/Maldivian
- Hebrew
- Kurdish (Sorani)
- Persian/Farsi
- Urdu
- Syriac
- Rohingya
- Fula
- N'ko
We will have to make the updates for the IP change language translations we added in issue #76 to include if anymore languages we have added thus far need to have ...
placed to the left of the text.
It is a great idea to move the useIPnfo() from the MasonryBox so that it doesn't have to be called every time upon clicking on a contributor.
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.
Brilliant! I didn't even consider the
...
for the languages that go from right to left. That is a great detail you have highlighted and added. @sherikovic. It took me a little bit to realize why you were moving the...
until I realized the language is written in the other language😅I ran a search, and other languages that are right to left are:
- Aramaic
- Azeri
- Dhivehi/Maldivian
- Hebrew
- Kurdish (Sorani)
- Persian/Farsi
- Urdu
- Syriac
- Rohingya
- Fula
- N'ko
We will have to make the updates for the IP change language translations we added in issue #76 to include if anymore languages we have added thus far need to have
...
placed to the left of the text.It is a great idea to move the useIPnfo() from the MasonryBox so that it doesn't have to be called every time upon clicking on a contributor.
Yea makes sense. I was thinking about that too, but wanted to try it out for Arabic first.
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.
@sherikovic I went ahead and went through your 11 file changes, and they look great! Thank you for taking the time to assist and make it more organized, code refracturing a bit, the addition on Arabic with customizing the text to display ...
to the left, and additionally making the IP component run more efficiently so it doesn't have to render every time when clicking on a contributor image to see their text.
You can go ahead and make your two proposed charges 🟢
- App.js l.21: there is margin and padding added on l.19 already —> can be removed (not changed)
- App.js l.18: onCategoryChange={handleCategoryChange} doesn’t seem to have any functionality, also there is no categories in the contributors JSON
And once you recommit and the preview link runs successfully again, we will merge this into the main!
Done! |
Great work, @sherikovic, for your detailed contributions to cleaning up the code and adding code logic to display |
Issue Addressed
I did a couple of cleanups and minor changes, also added Arabic translation with a position manipulation of the ... that follows "Before I Die"
Proposed Changes and Benefits
Notes to Reviewers
Checklist