Skip to content

add releasedOn date to new challenges#12720

Closed
QuincyLarson wants to merge 154 commits intofreeCodeCamp:stagingfrom
QuincyLarson:fix/add-old-back-end-projects-as-optional
Closed

add releasedOn date to new challenges#12720
QuincyLarson wants to merge 154 commits intofreeCodeCamp:stagingfrom
QuincyLarson:fix/add-old-back-end-projects-as-optional

Conversation

@QuincyLarson
Copy link
Copy Markdown
Contributor

@QuincyLarson QuincyLarson commented Jan 22, 2017

Pre-Submission Checklist

  • Your pull request targets the staging branch of freeCodeCamp.
  • Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
  • You have only one commit (if not, squash them into one commit).
  • All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

  • 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:

  • Tested changes locally.
  • Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

This adds a "releasedOn" date so they will get a "New" tag in the challenge map (though this feature has yet to be implemented in our reactified platform).

I also moved some of our retired backend projects into our "take-home practice projects" section so campers can still build them if they're looking for extra practice.

Finally, I fixed the "isRequired" flag for a couple of the intermediate algorithm challenges that were moved over from advanced algorithm challenges (and were previously un-required)

@QuincyLarson QuincyLarson added the status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. label Jan 22, 2017
@systimotic
Copy link
Copy Markdown
Member

@QuincyLarson

  1. Merge conflicts 😢
  2. The last commit seems to be doing something completely different from the rest of this PR. I think it would probably be easier to QA if they were separate PRs (that may have even been your intention).

@raisedadead raisedadead added the status: blocked In a transient & temporary hold. label Jan 24, 2017
@QuincyLarson
Copy link
Copy Markdown
Contributor Author

@systimotic I think this is ready. Please squash these commits when you merge this.

Copy link
Copy Markdown
Member

@no-stack-dub-sack no-stack-dub-sack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@QuincyLarson merging this as is would be problematic I think. See what I've noted below. This would splice 2 challenges together (object tests w/ array challenge), and it removes an additional test that was added to that last object challenge.

The content that you added in here has actually been moved up to the top as the first array challenge (it was just posted out of order on the GitHub thread).

This comment was marked as off-topic.

This comment was marked as off-topic.

@QuincyLarson QuincyLarson dismissed no-stack-dub-sack’s stale review January 31, 2017 20:13

OK - I've made these changes. Thank you for spotting these issues!

@QuincyLarson QuincyLarson force-pushed the fix/add-old-back-end-projects-as-optional branch from 8389a0d to bd88ac7 Compare January 31, 2017 22:55
@QuincyLarson
Copy link
Copy Markdown
Contributor Author

@no-stack-dub-sack OK - this should be good to merge. Please take another look when time permits :)

Leon Feng and others added 3 commits February 1, 2017 03:13
…llenge.

* Improve instruction.
* Format CSS values as table.
* Add additional test.
* Use strict equality check.
…html

Disable loopProtect for non-JavaScript code
Copy link
Copy Markdown
Member

@no-stack-dub-sack no-stack-dub-sack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@QuincyLarson I hate to do it to you 😧 , because I know you've been working on this for a while, but this needs one final change....

"assert.deepEqual((function() { delete user.data.friends; user.data.friends = ['Sam', 'Kira', 'Tomo']; return addFriend(user, 'Pete') })(), ['Sam', 'Kira', 'Tomo', 'Pete'], 'message: <code>addFriend(user, \"Pete\")</code> should return <code>[\"Sam\", \"Kira\", \"Tomo\", \"Pete\"]</code>');"
"assert('name' in user && 'age' in user && 'data' in user, 'The user object has name, age, and data keys');",
"assert((function() { let L1 = user.data.friends.length; addFriend(user, 'Sean'); let L2 = user.data.friends.length; return (L2 === L1 + 1); })(), 'The addFriend function accepts a user object and a friend as arguments and adds the friend to the array of friends in the user object.');"
],

This comment was marked as off-topic.

dhcodes and others added 7 commits January 31, 2017 21:57
- Apply appropriate formatting for key words
- Make algorithm image responsive
- Apply code tags around appropriate words
- Remove unnecessary semicolon in seed code
- Fix test with Infinity value
- Add solution to Breadth-First Search
…ion-bower

update bower.json with resolution for jQuery
…atting

Reformatted instructions for the first four ES6 challenges
…cription

Added a comma to separate x and y coordinates pairs
Greenheart and others added 15 commits February 10, 2017 19:06
Fix description of 2nd test in challenge Inventory Update
…decar

Chore(package): Remove gitter-sidecar due to vulnerability
Edited label text in description and challenge code
fix(challenge): added semicolon to statement, matching characters challenge
…mar-formatting-env-challenge

fix(challenge): various grammar and formatting, .env node challenge
…ion-ambiguity

Reword amiguous challenge instructions
…in-function-call

Ensure use of two arguments in function call
…e-tags

Remove code tags from challenge seed
@QuincyLarson
Copy link
Copy Markdown
Contributor Author

@no-stack-dub-sack Ok - I've made the fix you recommended, then rebased staging in and addressed the conflicts. Please double check, then squash and merge.

@QuincyLarson QuincyLarson removed the status: blocked In a transient & temporary hold. label Feb 12, 2017
@systimotic
Copy link
Copy Markdown
Member

@QuincyLarson This PR shows 154 commits for me, and still has merge conflicts. Is that intended?

@QuincyLarson
Copy link
Copy Markdown
Contributor Author

@systimotic yes - this branch has become quite ugly. I'm going branch of staging and re-apply the changes manually real quick, then put in a fresh PR.

@QuincyLarson QuincyLarson removed the status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. label Feb 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.