fix: add case for challenge type 31 in ChallengeTemplateView #1688
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
huyenltnguyen
approved these changes
Dec 9, 2025
Member
huyenltnguyen
left a comment
huyenltnguyen
left a comment
There was a problem hiding this comment.
Oh, sorry, I should have added this challenge type to mobile.
Previously review challenges had the generic type (24), but I added this new type so that I could use it to conditionally render a content outline (the same sidebar as the one on /settings). Though I haven't been able to get to this feature yet.
Related PR: freeCodeCamp/freeCodeCamp#61963.
I checked the main repo and there are challenges with type 24 still, so I think we should keep both.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist:
mainbranch of the repo.Not sure if we should keep 24 where it is?