Added Hyperlinks in Ways to Contribute Section#302
Added Hyperlinks in Ways to Contribute Section#302isabelcosta merged 17 commits intoanitab-org:developfrom anishfyi:hyperlink-contribution
Conversation
|
@daxoron I edited your PR description, to include |
isabelcosta
left a comment
There was a problem hiding this comment.
Nice work @daxoron !
Thank you for contributing 🙌🏾
src/Components/Home/index.js
Outdated
| <SectionSubheader title={section.title} /> | ||
| {section.content.map((content, indx) => { | ||
| return <Description key={indx}>{content.par}</Description>; | ||
| return <Description key={indx}>{HTMLReactParser(content.par)}</Description>; |
There was a problem hiding this comment.
this was needed to make text linkable right?
There was a problem hiding this comment.
@isabelcosta, Initially The Content Was Text, So React Could Easily Parse Text and Convert it To Equivalent Text Nodes but in Case You Have Any HTML Content Coming Inside the Content, We Needed to Help React To Parse The Content to be Treated as Valid and HTML Tags Passed To Be Converted To React Nodes, We Needed HTMLReactParser Which Converts HTML Tags To Equivalent React Nodes.
We Had Two Options 1.) dangerouslysetInnerHtml 2.) Third Party Library HTMLReactParser.
I Chose to Use HTMLReactParser because dangerouslyInnerHtml has some security concern and react may discard it in future versions, Thereby Used HTMLReactParser
|
@daxoron thank you for adding more context! Could you also fix the merge conflicts please 🙏🏾 I will request more reviews to get this approved :) |
| par: | ||
| "Each active repository has a stream to direct questions. \nIssues labeled as 'First Timers Only' are meant for contributors who have not contributed to the project yet. Please choose other issues to contribute to, if you have already contributed to these type of issues. \nMake sure to follow the Commit Message Style Guide when submitting PRs which will require review by at least one maintainer to be merged to the main code.", | ||
| 'Each active repository has a stream to direct questions. \nIssues labeled as <a href = "https://github.com/anitab-org/anitab-org.github.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22First+Timers+Only%22" target="_blank">First Timers</a> Only are meant for contributors who have not contributed to the project yet. Please choose other issues to contribute to, if you have already contributed to these type of issues. \nMake sure to follow the <a href = "https://github.com/anitab-org/mentorship-android/wiki/Commit-Message-Style-Guide" target="_blank">Commit Message Style Guide</a> when submitting PRs which will require review by at least one maintainer to be merged to the main code.', | ||
| }, |
There was a problem hiding this comment.
@daxoron can you update the hyperlinked text to "First Timers Only", right now it's just First Timers
Once done, this PR is good to go 🚀
There was a problem hiding this comment.
Also there are some conflicts, please resolve them as well
There was a problem hiding this comment.
@vj-codes Done. Modified Text and Resolved the Merge Conflicts.
|
@vj-codes @isabelcosta Merge Conflicts Resolved, Please Review and Merge. |
vj-codes
left a comment
There was a problem hiding this comment.
@daxoron Congratulations on your first contribution to the repository 🎉
LGMT!
|
@daxoron can you please check why the PR checks are failing? And hopefully, fix them 🤔 |
Yes, Checking Right Away 👍🏻 Will Make Necessary Changes by The End Of The Day 👍🏻 |
|
No urgency here @daxoron :) |
| with: | ||
| # Make sure the actual branch is checked out when running on pull requests | ||
| ref: ${{ github.event.pull_request.base.ref }} | ||
|
|
||
| # This is important to fetch the changes to the previous commit | ||
| fetch-depth: 0 |
There was a problem hiding this comment.
hopefully, the changes to this file won't be needed, as these are already on their way in this pull request #305. Could you take a look, and if you agree with the changes leave an approval @daxoron ?
There was a problem hiding this comment.
@isabelcosta its just a draft change because of the recent prettier change, My PR Checks Were Failing and nothing due to my code.
Will Update within sometime for the final change.
There was a problem hiding this comment.
yes, I understand :) If these changes help you and you approve the other PR, I can go ahead and merge it, and then you can get that change in your PR 😉 @daxoron
There was a problem hiding this comment.
@isabelcosta I Have Made Some Final Changes in deploy.yml aswell.
I Had A Look on #305 PR but those changes were not working with my PR.
So I have made the required changes and have a look and both #305 and #302 can be closed with my PR.
|
@isabelcosta My PR Checks Will Pass if #305 Gets Merged. |
|
The changes made in this PR were tested locally. Following are the results:
|
|
Thank you @daxoron for collaborating with @ftonato to get this completed 💪🏾 |
|
@isabelcosta Thank You For Assigning Me this Task. |

Description
Added Relevant Hyperlinks In Ways To Contribute Section
We Had Two Options 1.) dangerouslysetInnerHtml 2.) Third Party Library HTMLReactParser.
I Chose to Use HTMLReactParser because dangerouslyInnerHtml has some security concern and react may discard it in future versions, Thereby Used HTMLReactParser
Fixes #299
Type of Change:
Checklist:
Code/Quality Assurance Only