<!-- freeCodeCamp Pull Request Template -->
<!-- IMPORTANT Please review https://github.com/freeCodeCamp/freeCodeCamp/blob/staging/CONTRIBUTING.md for detailed contributing guidelines -->
<!-- Help with PRs can be found at https://gitter.im/FreeCodeCamp/Contributors -->
<!-- Make sure that your PR is not a duplicate -->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply. -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] Your pull request targets the `staging` branch of freeCodeCamp.
- [x] Branch starts with either `fix/`, `feature/`, or `translate/` (e.g. `fix/signin-issue`)
- [ ] You have only one commit (if not, [squash](http://forum.freecodecamp.org/t/how-to-squash-multiple-commits-into-one-with-git/13231) them into one commit).
- [x] All new and existing tests pass the command `npm test`. Use `git commit --amend` to amend any fixes.
#### Type of Change
<!-- What type of change does your code introduce? After creating the PR, tick the checkboxes that apply. -->
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
- [ ] Add new translation (feature adding new translations)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask in the Contributors room linked above. We're here to help! -->
- [x] Tested changes locally.
- [x] Addressed currently open issue (replace XXXXX with an issue no in next line)
Closes#17215
#### Description
<!-- Describe your changes in detail -->
Here are a list of style changes made for problems 1-16:
* 2: Centered text
* 6: Centered text and `<sup>` tags
* 8: Centered text
* 9: Centered text, `<var>`, and `<sup>` tags
* 11: Centered text and spacing between number grid and next paragraph
* 12: Tab spacing (padding-left: 4em)
* 14: Centered text, `<var>` tags, and tab spacing (padding-left: 4em)
* 16: `<sup>` tags
BREAKING CHANGE: None
Here's a list of style changes made for problems 17-26:
*17: Bold tags
*18: Bold tags
*19: ul and li tags for leap year information
*20: var tags and line break
*21: var tags
*22: added code tag
*23: var tags
*24: centered text and var tag
*25: sup tags, tab-like spacing, and CSS grid for spacing
*26: sub, sup, and var tags, and CSS grid for spacing
BREAKING CHANGE: None
This PR allows us to validate the schema during test.
It also removes some cruft from the seed files and ensures only the required data is packaged and consumable, reducing the package weight somewhat.
* fix(logs): Remove console.log's
* chore(challengeMap): challengeMap -> completedChallenges
* chore(userModel): Update user model
* feat(userIDs): Add user ident fields
* chore(github): Remove more refs to github data
Edited the description to more closely match the spacing and line breaks
from projecteuler.net. Added more tests, updated the challenge seed,
and added a solution from user @elliotjz contributed to the fCC
Arcade Mode.
BREAKING CHANGE: None
Changed the name of the function in the challengeSeed from euler49 to the
challenge name. Also added a solution that @elliotjz contributed to the
fCC Arcade Mode.
BREAKING CHANGE: None
Added `<sup>` tags to the description to make it more like the one on
projecteuler.net. Also added additional tests and a solution.
Here's a solution for QA:
```
```
BREAKING CHANGE: None
Updated the problem description with an inline CSS grid, <sup>, and
<var> tags. Also added a solution that user @elliotjz contributed
to the fCC Arcade Mode.
BREAKING CHANGE: None
Updated the problem description with <sup> and <var> tags, and centered
some text. Also, added a solution that user @elliotjz contributed to the
fCC Arcade Mode.
BREAKING CHANGE: None
Changed the "Build a Personal Portfolio" id in the
responsive-web-design-certificate tests to the correct id.
Users are now capable of claiming the "Responsive Web Design Certificate".
Updated the problem description to more closely match the one on the Project Euler page. Also added more tests along with a solution that user @elliotjz contributed to the fCC Arcade Mode.
BREAKING CHANGE: None
Updated the problem description with `<val>` tags and improved the
formatting. Also added a solution that user @elliotjz contributed to
the fCC Arcade Mode.
BREAKING CHANGE: None
Updated the problem description with <sup> and <sub> tags. Also added a
solution that user @elliotjz contributed to the fCC Arcade Mode.
BREAKING CHANGE: None
Updated the problem description with <i> tags. Removed a couple of tests
because they seemed too restrictive for the different approaches users
might take when solving this problem. Also added a solution
that user @elliotjz contributed to the fCC Arcade Mode.
BREAKING CHANGE: None
Originally the test would check for the index of a title in an array of
unique challenge titles. However, the index of the title within the
array isn't important for this test, so I simplified the code using
@Bouncey's suggestion in PR #17035.
Also changed grammar for the error that's thrown when a challenge
title isn't a valid string.
BREAKING CHANGE: None
Due to the recent problem with two challenges having the same title, I
added a check for unique titles to the test suite so that hopefully
won't happen again.
Addresses a comment in issue #16906, which was recently closed.
BREAKING CHANGE: None
Closes#16906
Rajat Kanti Nandi
Stuart Taylor
Bennett Elder
Kristofer Koishigawa
Mrugesh Mohapatra
Jarek Wojciechowski
Aditya Rohilla
Oliver
Marcin Procyk
Jake Magers
Irina Brennen
Courtney
Logan Wright
Emanuele Antonelli
matt lubel
Nicholas Nadeau, P.Eng., AVS
Ahmad Abdolsaheb
Shivam Chawla
Chaitanya
Kirushna Kumar
Varun
Quincy Larson
guiKailu
Hakeem Davis
Edit Bazso
Ákos
Bryan Williams