zc_expenses plungin

Creators:

HNG8 Team Grange

About

The Zuri expenses plugin hosted here is a plugin that allows users to create and publish expense list which can be viewed by everyone in the organisation

Resources

1. This is the link to the Design file
2. our repo the zc_plugin_expenses repo
3. the live server

Instructions

Instruction for backend endpoints creators

1. Please take note that all plugins should follow the route /api/v1/
2. After writing an api document it properly and make it available on /docs/v1
3. For each of the api created, create a test that will call it and validate that it is working. The test has to be online and hosted via /test/. Each test is a different task.

Setting up your environment

1. make a fork of the zc_plugin_expenses repo
2. clone the forked repo to your system
3. add a remote url pointing at the zc_plugin_expenses repo for fetches

Getting Tasks to work on

1. To get a task to work on, search for any unassigned issue on your preferred track(i.e design, frontend or backend) on the issues tab
2. take note of the issue number and indicate interest to work on the issue on Team grange slack channel
3. if approved the issue will be assigned to you
4. try to finish the issue as fast as possible to avoid reassignment
5. when done submit task

Submitting a task

1. after working on a task before committing, fetch from the zc_plugin_expenses repo to make sure your work is synced with others
2. after commiting make a pull request
3. in the title field write the team name i.e Team Grange, a very very brief descripton of the work done and also the number of the issues you worked on
4. make the pull request to the zc_plugin_expenses repo
5. locate the issue you worked on and on the descrition field write the team name i.e Team Grange, a very very brief descripton of the work done
6. also on the description field add a link to your work on the live server for developers and a link to your design file for designers
7. add a link to your pull request
8. and finally include a snapshot of your work on the live server or design file
9. submit the link to your issue on the slack #issue-review page tagging one of our mentors i.e(@Loy, @caculuz or @twanitoria) and the one team reviewer @Ammeromi or I @kelanialiyu

Coding Guidelines

1. create new files only when necessary
2. try to make all work look excactly like the designs
3. before writing any code on any file write a comment including your slack username and task issue number with start
4. then your code
5. and a comment including your slack username and task issue number withend keywords eg

//@kelanialiyu issue #123

function fancyAlert(arg) {
  console.log("Team Grange");
}

//@kelanialiyu issue #123

GOOD LUCK AND HAPPY CODING