You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-4Lines changed: 6 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -62,9 +62,9 @@ The goal of this exercise is to get you used to the TDD flow.
62
62
63
63
We've provided you with appropriate tests to guide and validate your solution. You need to make all the tests pass, one by one, by implementing the `load` method in the existing `RemoteFeedLoader` class.
64
64
65
-
1) Fork the latest version of the challenge repo.
65
+
1) Fork the latest version of the challenge repo. Here's <ahref="https://guides.github.com/activities/forking"target="_blank">how forking works</a>.
66
66
67
-
2) Open the `FeedAPIChallenge.xcodeproj` project.
67
+
2) Open the `FeedAPIChallenge.xcodeproj` project on Xcode 12.
68
68
69
69
3) There are two main folders in the project:
70
70
- The `FeedAPIChallenge` folder contains the production types, including the `RemoteFeedLoader` and dependencies for requesting and loading the feed remotely. ***You only need to change the `RemoteFeedLoader.swift` file to implement the `load` method.***
@@ -75,7 +75,9 @@ We've provided you with appropriate tests to guide and validate your solution. Y
75
75
76
76
5) While developing your solutions, run all tests with CMD+U.
77
77
78
-
6) When all tests are passing and you're done implementing your solution, create a Pull Request from your branch to the main challenge repo.
78
+
6) When all tests are passing and you're done implementing your solution, create a Pull Request from your branch to the main challenge repo **with the title: "Your Name - Feed API Challenge**.
79
+
80
+
**7) Post a comment in the challenge page in the academy with the link to your PR, so we can review your solution and provide feedback.**
79
81
80
82
81
83
## Guidelines
@@ -94,4 +96,4 @@ We've provided you with appropriate tests to guide and validate your solution. Y
94
96
95
97
7) Aim to write self-documenting code by providing context and detail when naming your components, avoiding explanations in comments.
96
98
97
-
8) Strive to produce a clean solution as it can be **an ideal addition to your project portfolio**!
0 commit comments