* fix(client): fix client
* fix propType and add comment
* revert user.json prettification
* slight type refactor and payload correction
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* update ChallengeFile type imports
* add cypress test for code-storage
* update test and storage epic
* fix Shaun's tired brain's logic
* refactor with suggestions
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* update codeReset
* increate cypress timeout because firefox is slow
* remove unused import to make linter happy
* use focus on editor
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* use more specific seletor for cypress editor test
* account for silly null challengeFiles
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: remove circular dependency
redux depended on templates/Challenges/redux and vice versa. This
meant that import order mattered and confusing bugs could arise.
(cherry picked from commit 7d67a4e70922bbb3051f2f9982dcc69e240d43dc)
* feat: require imports to be in alphabetical order
Import order generally does not matter, but there are edge cases
(circular imports and css imports, for example) where changing order
changes behaviour
(cherry picked from commit b8d1393a91ec6e068caf8e8498a5c95df68c2b2c)
* chore: order imports
* fix: lift up challenge description + title comps
This brings the classic Show closer to the others as they
now all create the description and title components
* fix: remove donation-saga/index circular import
(cherry picked from commit 51a44ca668a700786d2744feffeae4fdba5fd207)
* refactor: extract action-types from settings
(cherry picked from commit 25e26124d691c84a0d0827d41dafb761c686fadd)
* fix: lint errors
* feat: prevent useless renames
* 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.
