You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
We cannot create an ExpenseLog from the Schema
Specifications
Version:
The text was updated successfully, but these errors were encountered:
Expected Behavior
When
using
a MoneyLog one of the functions will be to log expenses that occur. This would involve a number of situationsPlanned 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 aLogCategory
and aPaymentMethod
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
Specifications
The text was updated successfully, but these errors were encountered: