feat(client): add project links to certificate#40071
feat(client): add project links to certificate#40071raisedadead merged 17 commits intofreeCodeCamp:mainfrom
Conversation
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
| {signedInUserName === username ? ( | ||
| shareCertBtns | ||
| ) : ( | ||
| <> | ||
| <Spacer size={2} /> | ||
| <ShowProjectLinks | ||
| username={username} | ||
| user={user} | ||
| name={userFullName} | ||
| certName={certTitle} | ||
| /> | ||
| </> | ||
| )} |
There was a problem hiding this comment.
| {signedInUserName === username ? ( | |
| shareCertBtns | |
| ) : ( | |
| <> | |
| <Spacer size={2} /> | |
| <ShowProjectLinks | |
| username={username} | |
| user={user} | |
| name={userFullName} | |
| certName={certTitle} | |
| /> | |
| </> | |
| )} | |
| {signedInUserName === username && shareCertBtns} | |
| <Spacer size={2} /> | |
| <ShowProjectLinks | |
| username={username} | |
| user={user} | |
| name={userFullName} | |
| certName={certTitle} | |
| /> |
I think we always want the share buttons to be there.
There was a problem hiding this comment.
The share buttons, or the projects? Currently, I have not changed when the shareCertBtns are visible (only when the camper views their own cert), but I made it so the ProjectLinks are only visible to everyone else (not the camper themselves)
There was a problem hiding this comment.
Sorry, I misspoke - I meant the projects. It seems a little weird (to me) that they are not visible when you're viewing your own cert. Let's leave this open until we've nailed down the technical issues.
| const renderProjectsFor = certName => { | ||
| return projectMap[certName].map(({ link, title, id }) => ( | ||
| <li key={id}> | ||
| <Link to={link}>{title}</Link>: {getProjectSolution(id, title)} | ||
| </li> | ||
| )); | ||
| }; |
There was a problem hiding this comment.
| const renderProjectsFor = certName => { | |
| return projectMap[certName].map(({ link, title, id }) => ( | |
| <li key={id}> | |
| <Link to={link}>{title}</Link>: {getProjectSolution(id, title)} | |
| </li> | |
| )); | |
| }; | |
| const renderProjectsFor = certName => | |
| (projectMap[certName] || legacyProjectMap[certName]).map( | |
| ({ link, title, id }) => ( | |
| <li key={id}> | |
| <Link to={link}>{title}</Link>: {getProjectSolution(id, title)} | |
| </li> | |
| ) | |
| ); |
This handles legacy certs.
I'm not sure what's the best way to handle a weird bug where the cert renders, but is not in either of the Maps. Maybe show
Something has gone wrong with this certification, please report this to our team
@ahmadabdolsaheb any thoughts?
There was a problem hiding this comment.
This was a silly oversight of mine. Thanks, Oliver.
The only cert currently not in the map is the Fullstack cert. Once. #39695 is complete, then it should be easy enough to add. Should I push something dirty (hardcoded) through, for this PR?
|
@ojeytonwilliams Oliver, I have pushed a hard-coded quick-fix for the Legacy Full Stack cert. The links go to the related campers certificate (thoughts?): |
|
I went ahead and replaced the a tags with the Link helper. That should handle things nicely. The hardcoded solution looks good, though I think we need to change the wording in that case. It should say something like
More hard coding, I know. |
|
@ojeytonwilliams Edit: Oh...they are different components.... |
This reverts commit a8b8d64.
ojeytonwilliams
left a comment
There was a problem hiding this comment.
LGTM 👍
Thanks for your patience as I reviewed this.
@ahmadabdolsaheb could you take a look before we ping Quincy for his input?
|
Thanks for the back-and-forth, Oliver. As far as my plans go, I have just pushed my final changes. Just pending others' input. |
|
@SKY020, thank you for your progress on this feature. Here are my humble thoughts:
However, it would be a good idea to get @QuincyLarson's feedback at this point to see if we are on the same line. |
|
@ahmadabdolsaheb Thank you, for the feedback.
|
|
Project Links are now always visible. Let me know, what/if to change the background of non-certificate content to. |
|
Unsubscribe me from this plz
…On Sat, Nov 7, 2020 at 6:09 PM Shaun Hamilton ***@***.***> wrote:
Project Links are now always visible.
Links to the project pages are now in bold.
Let me know, what/if to change the background of non-certificate content
to.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#40071 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGL7EQMLAVZX6LY56DZYFETSOXOSNANCNFSM4S4WCCHQ>
.
|
|
Hey @SKY020 First of all thanks for your work on this PR so far. This looks solid. I recommend using underline instead of bold, because underline is associated with clickable links. Even underlined text is less aesthetically pleasing, it ensures people realize these are clickable. Second, in this image, under the "built the following projects" text: https://user-images.githubusercontent.com/51722130/97606130-5baba180-1a07-11eb-9eac-0d20266a7e9a.png Those aren't project names, those are certification names. I just wanted to make 100% sure you weren't pulling from the wrong data. I do prefer the version you reference earlier: https://user-images.githubusercontent.com/51722130/97212305-1c3b4600-17b8-11eb-97c0-b255c5dbfee0.png Where there is a "Solution" link as well. |
|
@QuincyLarson Those screenshots are outdated. The certifications currently appear like this: |
|
Hey @ShaunSHamilton can we get a rebase. Sorry we merged a lot of commits in recently, thanks for your hard work on this. |










Checklist:
Update index.md)masterbranch of freeCodeCamp.Closes #38917