Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow creation of an ExpenseLog #116

Open
zacck-zz opened this issue Jul 2, 2018 · 1 comment
Open

Allow creation of an ExpenseLog #116

zacck-zz opened this issue Jul 2, 2018 · 1 comment
Assignees

Comments

@zacck-zz
Copy link
Member

zacck-zz commented Jul 2, 2018

Expected Behavior

When using a MoneyLog one of the functions will be to log expenses that occur. This would involve a number of situations

Planned expense

A user will have planned to acquire an item and will usually have added that item to a wishlist, then to a shopping list, then went ahead to purchase that item. After this purchase occurs a user will record the event.

Here we allow a user to log an expense that is associated with a LogCategory and a PaymentMethod

Impromptu expense

A user will have planned to acquire an item and will usually have added that item to a wishlist, then to a shopping list, then went ahead to purchase that item. After this purchase occurs a user will record the event.

Here we allow a user to log an expense associated with only aPaymentMethod

Ideally, a mutation in the Schema with an input object that caters for the both of these situations would work here

Actual Behavior

This behavior is not implemented at the moment

Acceptance Criteria

Our Schema allows the creation of ExpenseLogs using a mutation

Steps to Reproduce the Problem

  1. We cannot create an ExpenseLog from the Schema

Specifications

  • Version:
@zacck-zz
Copy link
Member Author

@WanjikuMac see this one should be straight forward one

@zacck-zz zacck-zz added this to the Milestone 1 milestone Jul 26, 2018
@zacck-zz zacck-zz removed this from the Milestone 1 milestone Aug 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants