It's such a cool feature to be able to set the initial value of a wallet.

The issue is that, should we ever need to sync (for whatever reason) the transactions with the wallet - we'd be in trouble because the original initial value has been overridden when new transactions we added.

I suggest storing this initial value in a separate variable within the wallet model

Version 3.18.0 of eslint just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

There have been updates to the enzyme monorepo:

• • The devDependency enzyme was updated from 3.7.0 to 3.8.0.

• The devDependency enzyme-adapter-react-16 was updated from 1.7.0 to 1.7.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the enzyme group definition.

enzyme is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency redux-devtools was updated from 3.4.2 to 3.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

redux-devtools is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 15.5.4 of react just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As react is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Right now the user has to select the category for each transaction. We can improve this by automatically selecting a category.

Option 1: Select the last used category

Option 2: Use KNN to make an educated guess on which category to pick.
Ideally we'd want to use the following features:

• day of the month
• transaction value
• transaction type (income / expense)

However, there is a worry here that changing the category after the user has entered the value could be confusing (since the category would change). A solution would be to identify the category based on just day of the month and type, then, once the user adds the value, we can run the algo again and suggest a new category

Commit 09fe4ac added the env file under git control. Since this is customizable for each user, it should not be overridden by github. We should have an example file that each user can customize for their own application.

I know we have env.local that overrides this file, but we should not have anything specified by default (privacy issue)

Version 4.9.6 of mongoose just got published.

This version is covered by your current version range and after updating it in your project the build failed.

mongoose is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

There have been updates to the enzyme monorepo:

• • The devDependency enzyme-adapter-react-16 was updated from 1.7.0 to 1.7.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the enzyme group definition.

enzyme is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency nodemon was updated from 1.18.5 to 1.18.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

nodemon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency mongoose was updated from 5.3.13 to 5.3.14.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mongoose is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Let's add some default categories for new users

• Travel
• Entertainment
• Transportation
• Eating out
• Medical
• Clothes
• Groceries
• Rent
• Services

The devDependency recharts was updated from 1.2.0 to 1.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

recharts is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

At the moment there is no way to cancel an edit transaction window. Let's add a cancel button

Wish

We should create a system where it is fairly easy to add (build) modules and add them to the app. Sort of like a plugin system.
For instance, I would like to have a module that tracks any mutual funds that I have and updates my financial worth on a daily basis.

Version 4.7.0 of redux-persist just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As redux-persist is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

User model

Fields

• Email
• Password (Salted)
• First Name
• Last Name
• Settings

Methods

• create
• read
• update
• login

There have been updates to the react monorepoundefined

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Need

Local installations of the app should not expose the user's local settings in commits.

Solution

• Create a new file called config.js.sample that has dummy data. Upon install, each user should copy that file as config.js and fill in their own personal info.
• Add the config.js file to .gitignore
• [Optional] If the config.js file is already under git control, remove it so it is no longer commited

The devDependency eslint-plugin-jest was updated from 22.5.1 to 22.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Main screens

Desktop version

I believe that while the web app will be used to add expenses, that will not be its primary use (I assume mobile versions will be mainly used to add transactions) but rather analysis. As such, the main screen should be a dashboard with the following

• A collapsible section that the user can use to add new transactions
• A list of the latest transactions added (maybe transactions for the current month?)
• A list of all wallets
• A list of budgets

Mobile version

The mobile app will be primarily used to add transactions, so that should be the primary focus of the main screen.

🚨 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, 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 organiszation’s settings page, under Installed GitHub Apps.

The devDependency recharts was updated from 1.4.1 to 1.4.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

recharts is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 1.3.1 of grommet just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As grommet is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 2.1.0 of codecov just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As codecov is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Specs for this task as WIP

We need to support two types of transactions

• Regular transactions (purchases, that are simply subtracted from the transaction's wallet total amount)
• Inter-wallet transactions (the amount is transferred from one wallet to another, i.e. they are subtracted from the source wallet and added to the destination wallet).
  • Issue: How can we support conversion transactions (i.e. wallet one has one currency, wallet two has a different currency).
    • One option is to detect if the wallets have different currencies and show a popup asking the user for the conversion rate. At some point we can even suggest a conversion rate based on some online conversion tools

Fields

• CreatedBy (FK on User)
• Wallet (FK on Wallet)
• Date
• Amount
• Details

If this is a transfer between wallets

• TransferredTo (FK on Wallet)

Thoughts about encryption (Later Edit)

(please note that the a similar thing would apply for wallet)

• If we want to encrypt the transaction object before storing it in the database, we would have to store Amount and Details in a field (called Data) and encrypt that entire dict on presave / decrypt on preload
• I would leave Date, Wallet and outside of the encrypted part because:
  • They do not provide any detailed information on the transaction (i.e. how much was spent or on what)
  • It would be easier to query the database and retrieve only the information needed when querying for a wallet (otherwise we'd have to pull everything, decrypt, and only after the decryption part eliminate what is not needed.

As such the database structure would be something like

{
  _id: ObjId
  CreatedBy: RefId(User)
  Wallet: RefId(Wallet)
  CreatedOn: Date // I renamed this from `Date` to avoid confusion with the `Data` field
  Data: {
    Amount: Number,
    Details: String
  }
}

One question is if the model would support this (if Data was encrypted, it would no longer be a Dict but rather a binary field).

One possible solution would be to store the encrypted data into a separate field, (i.e. EncryptedData) and decrypt it in preload (or whatever Mongoose's equivalent method is) then copy it into Data. At write, the Data variable would be removed (In this case, Data and Encrypted Data would be mutually exclusive fields in the database).
If encryption is used, then, the Data field would only exist in the model, and would not be persisted in the database)

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Specs

An user can have multiple wallets (e.g. Bank account, Investment account, Savings, etc).
Each wallet has one owner but can be shared with multiple other users (Question: Should we look into creating / defining groups?)

Fields

• owner
• name
• sharedWith (TBD: should this be a list or should it be an intermediary table?)
• value (the sum of all transactions for this account)
• settings {currency, formatting{currencySymbolPosition, decimalSymbol, thousandsSeparator}}
• currency (auto-formatted=)

Methods

• create
• read
• update
• delete

Other observations

• Only the owner can delete a wallet
• When the owner deletes a shared wallet, a notification should be displayed letting the user know that the wallet is shared with User X, Y and Z. The user can then either
  • Transfer the ownership to one of the users that wallet is shared with
  • Delete the wallet
• Any user that has access to the wallet can add transactions to it

The devDependency react-color was updated from 2.14.1 to 2.17.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-color is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency mongoose was updated from 5.2.14 to 5.2.15.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mongoose is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Description

The app should be a one stop application for personal finance. It does not, at least in the first version, intend to connect to any Bank API or automate expense management.

Key features to consider for development

(each of these will have its own task)

• Customizable output (decimal character, position of currency symbol, date format)
• encrypted data: all of an user's data is encrypted before being stored in the database (maybe with the password value). The idea is that this is personal information and it might be a good marketing hook.
• reports for a date range, with graphs (trendlines and piecharts)
• it would be cool to have some kind of analysis (like trend) or forecast
• comparisons against other users (anonymous, of the form: you are spending7% more per month than other people in your area). This must be done against a sort of centralized server.
• internationalization. We should write the code so that everything is easily translateable
• budgets (smart budgets)
• shared wallets

There have been updates to the react monorepo:

• • The devDependency react was updated from 16.6.1 to 16.6.2.

• The devDependency react-dom was updated from 16.6.1 to 16.6.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 2.4.0 of eslint-plugin-import just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-import is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

STR

• Go to any wallet's details page
• Make sure you have any transactions that have been edited or added for a different date (after a transaction with an ulterior date has been added)

Expected

• See transactions in the descending order of their dates

Actual

• Transactions are shown in the order in which they were entered in the DB

Version 15.5.9 of prop-types just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As prop-types is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

The devDependency supertest was updated from 3.3.0 to 3.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

supertest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴