Skip to content

Latest commit

 

History

History
170 lines (114 loc) · 6.8 KB

README.md

File metadata and controls

170 lines (114 loc) · 6.8 KB
Raw

Maintainability

Test Coverage

API Documentation

Backend delpoyed at Heroku

To get the server running locally:

  • Clone this repo
  • yarn or npm install to install all required dependencies
  • yarn or npm run server to start the local server
  • yarn or npm test to start server using testing environment

Backend framework goes here

The framework we chose is Apollo Server using GraphQL and Knex.

  • Point One
  • Point Two
  • Point Three
  • Point Four

2️⃣ Endpoints

Visit the local server in the GraphQL playground and with a valid token you can access queries and mutations for our server.

Optionally you can test these endpoints on Postman or Insomnia using the GraphQL selection. Every query and mutation are treated as POST requests.

GraphQL Queries

Method Endpoint Access Control Description
GET /organizations/:orgId all users Returns the information for an organization.
PUT /organizatoins/:orgId owners Modify an existing organization.
DELETE /organizations/:orgId owners Delete an organization.

GraphQL Mutations

Method Endpoint Access Control Description
GET /users/current all users Returns info for the logged in user.
GET /users/org/:userId owners, supervisors Returns all users for an organization.
GET /users/:userId owners, supervisors Returns info for a single user.
POST /users/register/owner none Creates a new user as owner of a new organization.
PUT /users/:userId owners, supervisors
DELETE /users/:userId owners, supervisors

Data Model

🚫This is just an example. Replace this with your data model

DRAFTS

{
  id: UUID
  name: STRING
  industry: STRING
  paid: BOOLEAN
  customer_id: STRING
  subscription_id: STRING
}

USERS

{
  id: UUID
  organization_id: UUID foreign key in ORGANIZATIONS table
  first_name: STRING
  last_name: STRING
  role: STRING [ 'owner', 'supervisor', 'employee' ]
  email: STRING
  phone: STRING
  cal_visit: BOOLEAN
  emp_visit: BOOLEAN
  emailpref: BOOLEAN
  phonepref: BOOLEAN
}

2️⃣ Actions

🚫 This is an example, replace this with the actions that pertain to your backend

getOrgs() -> Returns all organizations

getOrg(orgId) -> Returns a single organization by ID

addOrg(org) -> Returns the created org

updateOrg(orgId) -> Update an organization by ID

deleteOrg(orgId) -> Delete an organization by ID


getUsers(orgId) -> if no param all users

getUser(userId) -> Returns a single user by user ID

addUser(user object) --> Creates a new user and returns that user. Also creates 7 availabilities defaulted to hours of operation for their organization.

updateUser(userId, changes object) -> Updates a single user by ID.

deleteUser(userId) -> deletes everything dependent on the user

Environment Variables

In order for the app to function correctly, the user must set up their own environment variables.

create a .env file that includes the following:

_ STAGING_DB_URL - optional development db for using functionality not available in SQLite _ NODE*ENV - set to "development" until ready for "production"

  • JWKS*URI - Auth0 Jwks client connection
  • AUTH0*USERINFO - Auth0 domain with /userinfo endpoint to retreive user
  • AUTH0*AUDIENCE
  • AUTH0_DOMAIN

Contributing

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct. Please follow it in all your interactions with the project.

Issue/Bug Request

If you are having an issue with the existing project code, please submit a bug report under the following guidelines:

  • Check first to see if your issue has already been reported.
  • Check to see if the issue has recently been fixed by attempting to reproduce the issue using the latest master branch in the repository.
  • Create a live example of the problem.
  • Submit a detailed bug report including your environment & browser, steps to reproduce the issue, actual and expected outcomes, where you believe the issue is originating from, and any potential solutions you have considered.

Feature Requests

We would love to hear from you about new features which would improve this app and further the aims of our project. Please provide as much detail and information as possible to show us why you think your new feature should be implemented.

Pull Requests

If you have developed a patch, bug fix, or new feature that would improve this app, please submit a pull request. It is best to communicate your ideas with the developers first before investing a great deal of time into a pull request to ensure that it will mesh smoothly with the project.

Remember that this project is licensed under the MIT license, and by submitting a pull request, you agree that your work will be, too.

Pull Request Guidelines

  • Ensure any install or build dependencies are removed before the end of the layer when doing a build.
  • Update the README.md with details of changes to the interface, including new plist variables, exposed ports, useful file locations and container parameters.
  • Ensure that your code conforms to our existing code conventions and test coverage.
  • Include the relevant issue number, if applicable.
  • You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.

Attribution

These contribution guidelines have been adapted from this good-Contributing.md-template.

Documentation

See Frontend Documentation for details on the fronend of our project.