dpigeon / edge Goto Github PK

• Show two different buttons (like, dislike)
• Make them clickable
• Show the component overall.

• Every user has 1 like or dislike per post
• When user clicked, increment counter
• Create 2 counters (one for like and one for dislike)
• POST the counter
• GET the counter

Either:

• Edited on a new page
  Then:
• You cannot modify the email
• You can modify the last name, first name and password
• POST any changes to the server side once someone edits their settings

• Return the list of messages associated to the thread
• Should be on /message (or /thread) with GET request
• Can be of form /thread/:thread_id

• Using forms with #58 and #59, take all informations
• Create a button to POST the group to the JSON file
• Returns to the group page (GET groups you are in)

Expose an endpoint to allow front-end users to sign up. The front-end developers will know exactly at which path they have to send the JSON data for signing up new users.

Once button is clicked,

• Have an input of email receiver (To)
• Have an input of your user (From)
• Have a big form input for message (MessageForm)
• Cancel/Send message button

• Return the list of message threads associated to the user ID/email
• Should be on /messages (or /threads) with GET request
• Can be of form /threads/:user_id

/profile GET gets all information of that user.

/profile POST

Expose a rest endpoint so that the front-end can send HTTP requests for logging in as parents or teachers

• Get the JWT token to encode (backend)
• Get the JWT token to decode (frontend)
• Use localStorage to store token
• Attempt at least one integration success with login and signup

Either:

• Create a new page for it
  Then:
• GET email, last name, first name and other informations
• Create modules for that information to be displayed

Make the posts persistent in the database. Allow the front-end to query for all posts done by a certain user, all posts from a group, or all posts from the dashboard

-add a place for student profiles in the dashboard

On the next meeting (September 17th at 12:45PM), we are going to enhance our GitHub page.

• Retrieve Picture on post & comments
• Show it on dashboard

• GET the groups
• Users can see what groups they are in

Test:

We are going to use:

• Go Language for back end development
• AngularJS for front end development
• SQL (apache) for the database
• What's App for communication between team members

isn't T-06 and T-07 same?
what about 02 and 03?

• Non-Functional requirement

It would be nice if you could add the status image (badges or icons) that show the status of your build into your README file of the project.
For more info 👍 https://docs.travis-ci.com/user/status-images/

• Everything we had was converted to our new framework React.

• Create a new route for the page
• Design it with some CSS

• A simple link on profile of users
• Must be shown everywhere to access their walls

After the user sent a message by clicking on the button mentionned here #24,

• GET the message from server that was just sent
• Show its sender
• Below, show the input fields to reply like shown here #25

• POST who liked
• Increment counter found here #47

Under the messages threads,

• Show an input form
• Button to reply
  - Once clicked, POST message on server
  - Store in it dabatase

User:
- check if the user is a parent or a teacher
Validate the username:
- check if username exists in database
- check if the username is not empty
- check if its more than 5 character

Validate the password:
- check if the password is not empty
- check if a username exists in the database

Connect to the database with javascript
Tests to connect with backend

Low Priority Cases:

• Remember Me checkbox
• Caps locked on password
• Alert box under the button to see if successfully connected or not

• When the button is clicked on the group page, show it
• Show a form

• A field to post comments
• Button
• Unique backend ID of each post

/message POST Send a Single Message on a Thread

• Add a message to the current message thread
• Should on /message (or /thread) with POST request
• Can be of form /thread/:thread_id

• Upload button
• Upload the image to the server somewhere
• Dimension of image restriction

Closed because we will break down this big user story into small issues.

• POST the pictures to the wall
• Make a button to get picture on your own computer
• Restrict the dimension of a picture or resize it

• Form with the pictures
• Kind of like posts

• POST with id
• Be able to add many ids (username or email) separated with commas

• Required for the posts and comments on issue #11 .

• Get the date on the dashboard
• Be able to schedule things

The goal is to implement the basic logic of threads and messages.

A thread can be opened between two users.
Messages between two users can be added to the same thread.

The CRUD model should be respected and implemented for both threads and messages.

• GET who liked/disliked
• Integrate onHover when mouse if on button

• GET (request) the list of messages (threads) from the server
• Show the list
• No filtering needed
• Show a button on top left for a new message stated here #24

• GET the pictures once a wall is seen by someone
• Make some kind of dimension so that if picture is too big, resize it

• Use the Router React offers
• Redirects to one simple file called Routes.