* fix(client): undent dents caused by dedent
* remove one more unnecessary indent caused by dedent
* remove dedent
* add: dedent with no indentation
* correct line breaks
* feat: get helpCategory from frontmatter
* DEBUG: sets all the projects to JavaScript
This is just so the tests pass, it'll need to go.
* fix: updated helpCategoryMap categories
* fix: added Python to helpCategory frontmatter key
Co-authored-by: Randell Dawson <rdawson@onepathtech.com>
* fix: make help button use subforum topics
* fix: add test to check that block exists
Co-authored-by: ojeytonwilliams <ojeytonwilliams@gmail.com>
* fix: improve error message
* Update curriculum/test/test-challenges.js
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix(client): add warning on exceeding forum post length limit
Co-authored-by: Mrugesh Mohapatra <1884376+raisedadead@users.noreply.github.com>
* fix: corrected guide url for backend challenges and projects
* fix: moved getGuideUrl to utils
* fix: added forumTopicId to ChallengeNode PropTypes
* fix: conolidated helpers and add base url to env.json
* fix: made use template literals
* tests: created unit tests for getGuideUrl
* fix: add characters which will be encoded
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: use encoded version of title
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: encode title
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Per this: https://www.freecodecamp.org/forum/t/forum-suggestion-unformatted-code-warning/134857/24
`<code>` tags are not the semantically/idiomatically correct way to format code on Discourse. For example, `<code><span></span></code>` renders as that exact HTML, when the intention was almost certainly to render `<code><span></span></code>` instead.
