alexandria-reader/backend

Issues

• Allow linking words to their basic form

  #167 opened 2 years ago by TheChilliPL
  0

• chore: update github actions to use Node.js 16

  #158 opened 2 years ago by eamon0989
  0

• Internal Server Error whilst testing HTTP requests

  #155 opened 2 years ago by medic-code
  2

• @types/dotenv not necessary as a dev dependencies

  #150 opened 2 years ago by medic-code
  2

• API Documentation

  #154 opened 2 years ago by medic-code
  1

• feat: check database is available when backend starts

  #149 opened 2 years ago by eamon0989
  2

• Update readme for docker-compose instructions.

  #151 opened 2 years ago by medic-code
  3

• Implementing HTTPS and securing HTTP headers

  #153 opened 2 years ago by medic-code
  0

• Implement more best practices for the API

  #128 opened 3 years ago by mrchrmn
  1

• feat: add pagination

  #147 opened 2 years ago by eamon0989
  0

• Fix route tests to make them work with token authentication.

  #74 opened 2 years ago by mrchrmn
  0

• Add meaningful README.md

  #133 opened 3 years ago by mrchrmn
  0

• Inconsistent translation returns

  #130 opened 3 years ago by eamon0989
  0

• When updating translations, properties are sent back in snake_case and the context is not being sent to the frontend

  #131 opened 3 years ago by eamon0989
  5

• We need to investigate an admin dashboard that allows user administration

  #127 opened 3 years ago by mrchrmn
  0

• Return texts sorted by creation date

  #122 opened 3 years ago by mrchrmn
  0

• Users should only be able to retrieve their own texts.

  #121 opened 3 years ago by mrchrmn
  0

• Ignoring a word on the frontend seems to result in a 500 error on the backend

  #118 opened 3 years ago by eamon0989
  0

• We need to add a flag field in the database and add flags for each language.

  #109 opened 3 years ago by eamon0989
  6

• Build scripts

  #73 opened 3 years ago by mrchrmn
  0

• `GET /api/texts/` route should return only what the texts page needs.

  #98 opened 3 years ago by mrchrmn
  0

• For consistency, should `words.updateStatus` return the updated word rather than just the status?

  #88 opened 3 years ago by eamon0989
  3

• POST "http://localhost:3000/api/words/" should have duplicate verification.

  #93 opened 3 years ago by eamon0989
  3

• Newly added translations are not added to the `users_translations` join table, meaning they are not returned to the frontend

  #91 opened 3 years ago by eamon0989
  1

• Unique validation error when signing up with an existing email stops server from working.

  #90 opened 3 years ago by eamon0989
  0

• Modify POST route for words

  #79 opened 3 years ago by mrchrmn
  0

• Make words / translations routes work without word ids.

  #76 opened 3 years ago by mrchrmn
  0

• Translations that are already in the database are sent to the frontend as strings, they need to be converted to objects

  #83 opened 3 years ago by eamon0989
  0

• Word id's should be sent to frontend as `.id` instead of `word_id`

  #82 opened 3 years ago by eamon0989
  2

• `PUT /words` needs to get userId from token and have it removed from url

  #84 opened 3 years ago by eamon0989
  2

• Type changes to Userword and Translation

  #80 opened 3 years ago by mrchrmn
  0

• Add token middleware to all routes except login/signup

  #77 opened 3 years ago by mrchrmn
  0

• Add texts services

  #10 opened 3 years ago by danachen
  0

• Add words services

  #12 opened 3 years ago by danachen
  0

• Add words route

  #13 opened 3 years ago by danachen
  0

• Add translations services

  #14 opened 3 years ago by danachen
  0

• Add translations routes

  #15 opened 3 years ago by danachen
  0

• Test words routes and services

  #23 opened 3 years ago by danachen
  0

• Test translations routes and services

  #24 opened 3 years ago by danachen
  0

• Test texts routes and services

  #22 opened 3 years ago by danachen
  0

• Add users services

  #8 opened 3 years ago by danachen
  0

• Test users routes and services

  #21 opened 3 years ago by danachen
  0

• Add users route

  #9 opened 3 years ago by danachen
  1

• Add texts route

  #11 opened 3 years ago by danachen
  0

• Add routing/database structure per JS185 to project

  #2 opened 3 years ago by danachen
  0

• Add continuous deployment to Heroku to repo

  #4 opened 3 years ago by danachen
  1

• Set up application folder structure

  #1 opened 3 years ago by danachen
  1

• Finalize DrawSQL diagram and export DB model to repo

  #3 opened 3 years ago by danachen
  1