-
Notifications
You must be signed in to change notification settings - Fork 17
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
Pay Periods - Query Methods / Properties #19
Comments
Might be a good idea to split this up into some smaller issues... |
jantman
added a commit
that referenced
this issue
Apr 3, 2017
jantman
added a commit
that referenced
this issue
Apr 3, 2017
jantman
added a commit
that referenced
this issue
Apr 5, 2017
…action for the pay period, as well as method to get a list of all transactions as dicts, in display order
jantman
added a commit
that referenced
this issue
Apr 5, 2017
jantman
added a commit
that referenced
this issue
Apr 5, 2017
jantman
added a commit
that referenced
this issue
Apr 6, 2017
…ons from BiweeklyPayPeriod.transactions_list
jantman
added a commit
that referenced
this issue
Apr 6, 2017
…rn a dict of the budget amount, allocated amount and spent amount
jantman
added a commit
that referenced
this issue
Apr 6, 2017
…d spent). Need to figure out how to denote income.
jantman
added a commit
that referenced
this issue
Apr 6, 2017
jantman
added a commit
that referenced
this issue
Apr 7, 2017
jantman
added a commit
that referenced
this issue
Apr 7, 2017
jantman
added a commit
that referenced
this issue
Apr 7, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To enable the rest of the PayPeriod-related issues ( #34 #35 #36 #37 ), the PayPeriod object should have the following methods which take a
db_session
(a sqlalchemy.orm.scoping.scoped_session or a sqlalchemy.orm.session.Session) and return a sqlalchemy.orm.query.Query (we assume that in most cases we'll just be calling.all()
on this Query, but we should return the Query itself for flexibility):And the following methods which take a
db_session
and return a dict or object to be used by something downstream:BiweeklyPayPeriod._dict_for_sched_trans()
- set a budget start date at the beginning of the second week of a month, so we have a block of 3 consecutive pay periods, the first and last of which span month changes and the middle of which does not. Generate ~56 Monthly ScheduledTransactions on consecutive days, so we have transactions for at least one week on either side of the block of 3 consecutive pay periods. Ensure that each of the 3 pay periods contain the right transactions in the right order.Also:
biweeklybudget.settings_example.PAY_PERIOD_START_DATE
should be set to the closest Friday to the current date.The text was updated successfully, but these errors were encountered: