I need a front end component in which you can add categories to and have a column for Name, Budgeted value and actual value. The values should be summed at the bottom of the table.

Currently the text shoots to the left and because on the increase in size of the input box the css for the summary line goes all wonky.

I want the text to remain right so that it stays in line with the rest of the numbers and I want the size not to increase and mess up the vertical alignment.

Ask me if you need more info.

Would be cool if on successful push to heroku circle ci could take the version out of the package.json and use that number to make a git tag to denote the version that was just released to prod.

I'm currently using the third party stripe checkout component and I'm wondering if it might be better or worse if I switch to using the component that stripe has now released themselves. Have a look at and if it seems good might be worth changing over.

Currently don't have linting jobs in either the client or the server. I want to add both eslint and prettier into these. Also setup a lint:fix job to auto fix things.

Currently we're just deploying from the develop branch straight to what would be prod. There is not develop heroku app to deploy to. I need to setup a heroku app that will be deployed to from the develop branch and use the same environment variables as what I'm using for local development so it will hook up to the development database etc. Then I can use the current app for prod which will get deployed to from the master branch only. This will give me the ability to deploy to a live instance without breaking my current working copy of the application.

Make it so that circle ci runs a lint over things when you check in new commits. Requires #5 to be done first.

Add some husky hooks to make it so that linting gets done on commit and both lint and run the tests on push. Requires that #5 be done first.

Mlab's is shutting down would be good to move over to mongo atlas just to make sure I'm keeping up with the times.

I still have it set up to use the old api/app Google+ way of doing things I should change that over to use the new Google live api's

I'm going to have to

• Add actions to amend state for the summary lines on the budget app
• Make sure that the total values update the way that we'd expect. (they should because there are tests)

At the moment client lives in the server folder, essentially this makes the server folder the root of the application which means we need to push a subsection of the repo to heroku and this is annoying, I want to be able to just push this repo as is to heroku. So we need to split the client out from the server and then create root level files in this repo that can be used to start everything up in heroku and locally.

Need to make a readme that explains how to set this whole thing up and get it running. Both for development and how to spin up a prod environment.

Want to make something that pushes the code to heroku only in circle ci only when code is pushed to the master branch. Need to make sure that the code isn't pushed to heroku when you push to just any old branch needs to be only the master.

I want to look into GraphQL and if this is a good tech to use in this application. If it seems to fit then it would be good to bring in to learn about it.

Circle ci has the ability to set up jest so that in the pipeline runs you can see the results of the tests. See this link:

https://circleci.com/docs/2.0/collect-test-data/#jest

This will need to include a spike at the beginning to work out if Circle CI is even something I'm able to use personally. If it is I'd like to hook it up so that it does the following so far:

• Runs front end tests on PRs (in future it'll run back end tests as well)
• Runs linting on PRs
• Pushes the solution to heroku on merge to master