Skip to content

Commit e72fbd7

Browse files
Merge branch 'master' of github.com:Coderockr/backend-test
2 parents 84c1658 + ec3fee6 commit e72fbd7

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,10 @@ __NOTE:__ the implementation of an interface will not be evaluated.
1212
2. __Event details:__ the application must allow the user to see the details of the event, by clicking on the event listing, or accessing the event link;
1313
3. __User signup:__ the application should allow the user to register by informing: Name, Email, Password, Bio, Profile Picture, City, and State;
1414
4. __User login:__ The application should allow the user to login using their credentials;
15-
- 4.1 The login should persist when the application is closed, or updated;
15+
- 4.1 The login should persist when the application is closed, or reloaded;
1616

1717
### Logged Area
18-
5. __Friend invitation:__ the application will accept the user to enter an email to add as a friend;
18+
5. __Friend invitation:__ the application will allow the user to enter an email to add as a friend;
1919
6. __Add as friend:__ The informed user should receive a friend request, or an invitation to register, if they are not already a user;
2020
7. __Friendship management:__ the user will be able to see your new friend requests, list your friends, and undo friendships;
2121
8. __Event registration:__ the application should allow the user to register an event by informing: Name, Description, Date, Time, and Place;
@@ -35,7 +35,7 @@ __NOTE:__ the implementation of an interface will not be evaluated.
3535

3636
## Deliverables
3737
The project source code and dependencies should be made available in GitHub. Here are the steps you should follow:
38-
1. Create a public repository on GitHub (create an account if you don't have one).
38+
1. Fork this repository to your GitHub account (create an account if you don't have one, you will need it working with us).
3939
2. Create a "development" branch and commit the code to it. Do not push the code to the master branch.
4040
3. Include a README file that describes:
4141
- Special build instructions, if any
@@ -63,4 +63,5 @@ Use the following checklist to ensure high quality of the project.
6363
2. Briefly describe how you decided on the tools that you used.
6464

6565
## Have Fun Coding 🤘
66-
This challenge description is intentionally vague in some aspects, but if you need assistance feel free to ask for help.
66+
- This challenge description is intentionally vague in some aspects, but if you need assistance feel free to ask for help.
67+
- If any of the seens out of your current level, you may skip it, but remember to tell us about it in the pull request.

0 commit comments

Comments
 (0)