jmaicaaan/express-starter-ts

This repository gives the developer an Express Starter written in Typescript to kick off there development fast 🔥🔥🔥

express-starter-ts's Issues

Create a documentation for the object definitions

• Entity definition -> let's stick to call this as entity instead of model

• Controller definition

• Service definition

• Repository definition

Password and access token bcrypt

Refactor npm run script for setup:config

Currently, it is gulp createTravisBeforeScript I think it would be better to align the execution into the name of the run script.

Edit migration scripts.

use generate command to map the entity instead of manual mapping

Use the routing controller authorized inject instead of creating a middleware (ACL)

https://github.com/typestack/routing-controllers#using-authorization-features

Refactor configuration. Minimize the config files

Initial seed

• Initial admin account

• Initial user account (non-admin)

• Initial roles (User and Admin)

Use tsconfig.json paths into dist folder

Currently, we have the paths in the tsconfig.json where we can use as a path to the specific folders. However, that is only in the Typescript world (src) not in the distribution.

README simplification

Reference: https://gist.github.com/PurpleBooth/109311bb0361f32d87a2

Travis CI

Resetting of database in the TEST environment

Swagger

Add travis build status in the readme

Re-structure folder

As discussed, we will have some folder structures in our src folder to minimize the folders or the confusion for the developers as it currently mixing the app files and with the migrations and seeds.

Proposed folder structure
As discussed, we will have some folder structures in our src folder to minimize the folders or the confusion for the developers as it currently mixing the app files and with the migrations and seeds.

Proposed folder structure

• src
  • app
    • controllers
    • common
      • enums
      • middlewares
      • repositories
      • services
      • utils
    • entities
    • tests
  • migrations
  • seeds
  • server.ts

@ciiidi, let me know your thoughts with my proposed folder structure & let's add this into next branch!

Use mocha-typescript test

Authentication using repository of typeorm

Data seeding management

• Remove the initial seed under migration. A migration should not have a seeding!

Try using the @transaction() decorator in the controller definition

Add support for two factor authentication!

Fix documentation image

@ciiidi, I think the shareable link in the google photos expires every month? If we can manage this in the google settings about this, let's do it otherwise I will create a dropbox for us.

Make the documentation short and on point

Create CLI Tool

Create CLI tool similar to Angular CLI and create-react-app.

Prefix routes by /api

Take a look at the vscode auto importing

Vs code auto import can cause problems as it imports the class as module

Remove unused git branches

[Implementation] Repository pattern for the entities

Start with the with basic entities such as Account, AccessToken and Role

Enhance gulp generators

Gulp - Reusable tasks

Our generators would typical use the same tasks with different paths. I think it is much better to create a reusable tasks to reduce codes, file size and a more concise code to everyone.

Database migration 🔥

Documentation image - hosted

We have our folder for the documentation image in our source code which addends into the source size, let's move documentation images in a hosted server and insert the link in the README.md

Use class validator

Refactor test scripts.

Add tests for:
-unit
-end 2 end
-integration

Sit the test next to implementation. There is WIP of this on the next branch

Implement a class based seeds

[Feature] Hook up typeorm implementation

Let's make use of the ActiveRecord implementation, you can find an example at their github

• Unit Test

• Add example with the Account entity