crudjs / rest-nestjs-postgres Goto Github PK

View Code? Open in Web Editor NEW

145.0 145.0 53.0 402 KB

CrudJS implemented as a REST API, using Nest.js and Postgres

License: Apache License 2.0

JavaScript 0.39% TypeScript 99.61%

blog boilerplate crud nest nodejs postgres typeorm typescript

rest-nestjs-postgres's Introduction

CrudJS

Helps you build an awesome Node.js-based API

Intro

There are dozens of Node.js frameworks out there. Same is true for databases and the rest of the pieces. If you want to build an API these days, it gets increasingly difficult to choose a specific tech stack to start working with.

In other words, CrudJS intends to be the TodoMVC of Node.js-based APIs.

API details

In a few words, the CrudJS is a basic blog API, with entities such as 'entries' (like posts), 'authors' and 'categories', and with basic create/update, read and delete capabilities for each entity. 'Entries' should be considered the main entity.

You can use CrudJS...

For comparing between different Node.js API frameworks: how their code looks like, which code style you like the most, which is the most performant and/or stable...
For code reference when hacking something.
As a boilerplate for starting a new cool project.

Flavors

REST + Nest.js + Postgres - currently at version 1.0.0-alpha.1
Fastify + RethinkDB - coming soon
Express.js + MongoDB + Mongoose - coming soon
Hapi.js + DynamoDB + Dynamoose - coming soon
Koa - coming soon
Serverless - coming soon
Micro
...

Versioning

The idea is to build new features incrementally on every CrudJS flavor. Hence, you can expect each version to have the same set of features across all the flavors.

Please note that the scopes for versions > 1.0.0 is still tentaive.

^1.0.0

Basic CRUD functionality for entries, authors and categories.
Ability to get all entries for a specific author.
Ability to get all entries for a specific category.
Protected POST and DELETE methods for every endpoint.
Unit tests.
Auto-generated Swagger definition file.

^2.0.0

Readers can "cheer" an entry (anti-SPAM measures needed.)

^3.0.0

Realtime capabilities (new cheers notifications...)

Contributing

Of course, the project is open to contributions. Just leave a note!

rest-nestjs-postgres's People

Contributors

Stargazers

Watchers

Forkers

fiodor94 rpascual0812 zorioning dewdad asheliahut cleciobarbosa quynhlx morozov-dmitry hoangchien97 tdh4vn aqib-dev sergioutama churabou mwaszkiewicz anglesen1120 feidianbo paradigmajs yazart dirmich phiphop florianbouron arcanoix vchumakovv-hub vqoph khalidraufsmd bcdevlucas misterpoloy sandrorock rezagazeri iamvena wassimoo aryaw wilfernandesjr anoopk-extentia robsongade lazycoder10 vishalindev vigenteadmin uxuip nadeera3784 uraman2000 leducnikos alexmayberry rebaeksoparkkitchen duynd0909 artemov34 mehrnooshskh somaychauhan raghuraghavan rinsafathima nyhxiaoning walidhelaoui

rest-nestjs-postgres's Issues

some typeorm entity listeners not firing

the typeorm @AfterLoad is working
however, the @BeforeUpdate, @AfterUpdate, @BeforeInsert, etc are not

using postgres with logging enabled. I can see the UPDATE transaction run, and I also see the AfterLoad debug message

verified it is not typeorm, as I have tested using their template app and the same entity

@AfterLoad()
  afterLoad() {
    console.log('afterLoad');
  }

  @BeforeUpdate()
  beforeUpdate() {
    console.log('beforeUpdate');
  }

  @AfterUpdate()
  afterUpdate() {
    console.log('afterUpdate');
  }

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.