Create team.js

[arpit9667]

Description

Added model for the Team

Issue

Closes #547

Impacted Area

Main page

Steps to test

Steps needed to reproduce the scenario from this change to validate if the pull request solve this issue

• Create a team containing the users.

[alexanmtz]

@arpit9667, thanks for the Pull Request. This is not enough to set up the models in a Node application using equalize, you need to create a migration.

You need to do something like:
sequelize migration:generate --name name-of-your-migration

Check our current migrations to see how it works

[alexanmtz]

Great @arpit9667, but we have an issue when run the migration:
https://circleci.com/gh/worknenjoy/gitpay/1403?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link

Unhandled rejection SequelizeBaseError: column "TeamId" does not exist

[arpit9667]

@alexanmtz How to run the migration? I have created the migration for Team but the table is not getting created in the database.

`

[alexanmtz]

@arpit9667 you can run the migration with npm run migrate

[arpit9667]

@alexanmtz
The last two migration files are not running.
== One for the Plans Table
== One for the Teams Table
I think this is the problem. Can you check please?
Locally Also when I try to run the npm run migrate command. The two tables are not getting created in the database.

[alexanmtz]

@arpit9667 , if you run the migration already, you would need to drop the database and create again to run from scratch

[alexanmtz]

@arpit9667, there's changes on Plan model that should not be included.

Maybe you're not in sync with the upstream master.

[arpit9667]

@alexanmtz Yes, that was the problem. Now I have pulled all the changes for the master. Also I have implemented the Team model with the migrations that are needed. But, why is there a change for package-lock.json? Please help me with that.

[alexanmtz]

Thanks for the update @arpit9667, but it seems that makes sense the user be able to join many teams

[alexanmtz]

@arpit9667 yeah, the package-lock.json should not be included on the commit, because there's no new library installed, you should commit only the files required for this PR, otherwise, we may have conflict when merging.

You can maybe check the file from master (needs to be an updated master) with git checkout master -- package-lock.json (I think, please research about it).