Skip to content
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

feat: add legacyCertsSelector to Map component #54854

Conversation

Sembauke
Copy link
Member

@Sembauke Sembauke commented May 17, 2024

This adds a legacyCertsSelector to tell if a legacy cert is claimed on the superblock ribbons.

Before:
image

After:
image

The python certification isn't marked as a legacy cert yet, but is already being placed in the map as a legacy cert. Nor does it have a ribbon.

The Legacy responsive web design icon was already showing up as filled (with ribbon) as we use the same Certification enum for the new one. Which led to it being already filled.

@github-actions github-actions bot added the platform: learn UI side of the client application that needs familiarity with React, Gatsby etc. label May 17, 2024
@Sembauke Sembauke marked this pull request as ready for review May 17, 2024 07:41
@Sembauke Sembauke requested a review from a team as a code owner May 17, 2024 07:41
@Sembauke Sembauke added the status: blocked Is waiting on followup from either the Opening Poster of the issue or PR, or a maintainer. label May 17, 2024
@moT01 moT01 added status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. and removed status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. labels May 20, 2024
@sidemt
Copy link
Member

sidemt commented May 21, 2024

Thank you for working on this, @Sembauke!

As I mentioned in the staff chat, I (and Oliver) would suggest not showing the ribbon for Legacy Responsive Web Design Challenges here, since only the challenges are marked as legacy and listed here.

The same for the Legacy Python for Everybody. I think we don't need to show the ribbon for it.

@Sembauke
Copy link
Member Author

Hey @sidemt,
I will close this pull-request and open a new issue with your comment! I was a bit to quick on this :)

@Sembauke Sembauke closed this May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform: learn UI side of the client application that needs familiarity with React, Gatsby etc. status: blocked Is waiting on followup from either the Opening Poster of the issue or PR, or a maintainer.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants