Skip to content

Latest commit

 

History

History
102 lines (69 loc) · 2.54 KB

README.md

File metadata and controls

102 lines (69 loc) · 2.54 KB

frontend-api-challengev2

Project setup

yarn install

Compiles and hot-reloads for development

yarn run serve

Compiles and minifies for production

yarn run build

Run your tests

yarn run test

Lints and fixes files

yarn run lint

Customize configuration

See Configuration Reference.

Chitter API Frontend Challenge

  • Challenge time: rest of the day and weekend, until Monday 9am
  • Feel free to use Google, your notes, books, etc. but work on your own
  • If you refer to the solution of another coach or student, please put a link to that in your README
  • If you have a partial solution, still check in a partial solution
  • You must submit a pull request to this repo with your code by 9am Monday morning

Summary

This is a frontend for a twitter style api backend.

Technologies used were JavaScript and VUE 3.

The following interactions have been implemented:

  • Creating Users
  • Logging in
  • Posting Peeps
  • Viewing all Peeps
  • Viewing individual Peeps
  • Deleting Peeps
  • Liking Peeps
  • Unliking Peeps

Installation

Fork this repo and in the project directory:

yarn install yarn run serve

To run unit tests run:

yarn run test

Challenge:

As usual please start by forking this repo.

We are going to write a small Twitter clone that will allow the users to post messages to a public stream.

The scenario is similar to the Chitter Challenge, except someone has already built a backend API for you and hosted it on Heroku.

Your task is to build a front-end single-page-app to interface with this API. You can do this in any framework you like, or in pure Javascript. The API documentation is here.

Here are some interactions the API supports. Implement as many as you see fit.

  • Creating Users
  • Logging in
  • Posting Peeps
  • Viewing all Peeps (I suggest you start here)
  • Viewing individual Peeps
  • Deleting Peeps
  • Liking Peeps
  • Unliking Peeps

We are looking for well tested, easy to read, easy to change code. This is more important than the number of interactions you implement.

Note that others may be doing the same task at the same time, so the data may change as you are using it.

Utilities you might find useful