larongbingo / librarysystem-backend Goto Github PK

Instead of having each user info having its own mutation object, why not create a mutation object that handles all of the user info changes.

This is part of the refactoring.

This is to enact the GNU License in all source files

Need to clean up and refactor to improve readability

Create admin APIs for the ADMINISTRATOR userType

Since webpack compiles all of the code into a single file, we need to run webpack again to compile the files at /lib to preserve the dbSync and dbRand scripts

Put all values that isn't changing into const vars

Since we pushed the mysql credentials here and the repo is going public again, we must create a new credentials once the app is on production

We need to setup the follwing:

• Allowing GraphQL to handle file transfer
• FTP at Express
• Adding LARGEBLOB at a Sequelize Model

If you changed your username or password, and tried to use your current JWT for other transactions, it would pass through.

It needs to either give the user a new JWT or make their current JWT invalid.

Response/Message:

{
  "errors": [
    {
      "message": "Cannot read property 'userId' of undefined",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "borrowBook"
      ]
    }
  ],
  "data": {
    "borrowBook": null
  }
}

Input/Request:

mutation{
  borrowBook(userId:1,bookId:2, transactionRemark:"asd",token:"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6ImFkbWluIiwidXNlcklkIjoyLCJwb3NpdGlvbiI6IkFETUlOSVNUUkFUT1IiLCJpYXQiOjE1MjIyMjk4MzR9.IcMuLSEBLWV8RA8A_UA-MAdHcHGG0xYjM0VAduF7sEI")
}

To limit 1 Token to 1 Device, we need store the client information into the Sessions Table

Since most searches will be focused on keywords, where statements will not work.

Adding status code or error code at the responses would make checking for what happened at the front end easier.

Log something that will notify the dev that the APIs is connected to either IBM MySQL or Local

We have an error showing when building bcrypt-nodejs at Webpack

Store all of the error messages somewhere so that we can check and fix all bugs or errors in production

Instead of each API having its own insert statement for each API endpoint, why not move the logging of transactions to its own function to shorten code length at each API.

Since we are planning to add HTTPS (including the certs and everything), we will not be able to make the repo public since the IBM Cloud requires all of the files to put in the repo itself.

We need to search a script to add SSL Certs.

Currently we can only Create Books and Users, and Users the only having Update. We need to also make the other DB Operations to other Tables at the DB.