summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* Extended feat-fixated-prices.testJohn Wiegley2010-06-221-0/+12
|
* Price annotation no longer inject an implied costJohn Wiegley2010-06-226-3155/+2972
| | | | | | | | | | | | | | | | | | | | | | | Consider the following transaction: 2010-06-22 Sample Assets:Brokerage 10 AAPL {$30} Assets:Brokerage Previously, this would have been equivalent to: 2010-06-22 Sample Assets:Brokerage 10 AAPL @ $30 Assets:Brokerage However, this is not always what the user expects to happen. When @ is not being used, the transaction should reflect a mere transfer of commodities. This is now how it works, and thus the above transaction is now equivalent to the following instead: 2010-06-22 Sample Assets:Brokerage 10 AAPL {$30} Assets:Brokerage -10 AAPL {$30}
* Regression and generate tests now fail properlyJohn Wiegley2010-06-222-12/+18
|
* Added new --bold-if optionJohn Wiegley2010-06-221-0/+0
|
* Fixed typo in previous commit's regression testJohn Wiegley2010-06-211-1/+1
|
* bal was sometimes reporting empty accountsJohn Wiegley2010-06-211-0/+17
|
* Change weighting of account-name abbreviationJohn Wiegley2010-06-215-8/+8
| | | | | Parent accounts are abbreviated even more, so that child accounts can show more text.
* Added a regression test for the previous commitJohn Wiegley2010-06-211-0/+12
|
* Added tests for sole budget/forecast reportsJohn Wiegley2010-06-212-0/+86
|
* Don't warn about --import in doc when --no-pythonJohn Wiegley2010-06-201-1/+8
|
* Added missing call to resolve_end() in find_periodJohn Wiegley2010-06-201-0/+72
|
* If fixated price commodities are mixed, show themJohn Wiegley2010-06-201-0/+33
| | | | | | | | | | | For example, if a Ledger file contains transactions with the use of both EUR and EUR {=PRICE}, then regular reports will always show the {=PRICE}, disabling the by-name commodity merging that takes place. In brief, fixated and non-fixated commodities are now non-mergable. If a file contains all of one, or all of the other, they will still be merged, since these separate usages do not conflict the way that fixated and non-fixated together do.
* Regression test for last commitJohn Wiegley2010-06-201-0/+24
|
* Subsantial fixes and improvements to budgetingJohn Wiegley2010-06-194-5/+116
| | | | | | | | | 1. A bounded budget "from DATE to DATE" will now generate entries throughout that entire range, if it is triggered. 2. An unbounded budget begins, as before, in the timeframe of the reported posting which triggered it, but now continues until the present date.
* Fix to the way simplified regressions tests are readJohn Wiegley2010-06-191-1/+1
|
* Corrected a bug in report query parsingJohn Wiegley2010-06-191-4/+4
|
* Added new option --inject=KEY[,KEY...]John Wiegley2010-06-181-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you have a typed metadata key which contains an amount, you can use --inject=KEY to inject a posting with that amount wherever a match occurs. There are two main forms of usage: 2010-06-18 Sample ; Key:: $100 Expenses:Food $100.00 Assets:Checking The command would be: ledger reg --inject=Key In the above, transactional form, a posting under the account "Key" will be injected before the first posting reported for this transaction. It's amount will be $100. This only happens once for the whole transaction. It is also possible to associate the key with a posting: 2010-06-18 Sample Expenses:Food $100.00 ; Key:: $100 Assets:Checking Now the injected posting is generated whenever that particular post is reported.
* Created a script to check commenting coverageJohn Wiegley2010-06-151-0/+121
|
* Ensure that all options are tested and documentedJohn Wiegley2010-06-1520-0/+80
|
* Removed unused --unsorted optionJohn Wiegley2010-06-153-3/+3
|
* Tests run in parallel with using acprep -jX makeJohn Wiegley2010-06-153-23/+104
| | | | | This is done using the multiprocessing library in Python 2.6. If that's unavailable, this feature does nothing.
* Improved algorithm for abbreviating account namesJohn Wiegley2010-06-1433-215/+215
|
* Made >>>2 and === optional in regression testsJohn Wiegley2010-06-141-5/+6
|
* Corrected bug with forecasting date bounded xactsJohn Wiegley2010-06-132-37/+39
|
* Add support for typed metadataJohn Wiegley2010-06-121-0/+2
| | | | | | | | | | The metadata construct 'Key: Value' is now just a special case for 'Key:: "Value"'. Another after a :: in metadata setting is parsed as a full value expression and typed as such. For example: ; Key:: $400 + $500 ledger -l 'tag("Key") < $1000'
* The --anon option now randomizes its effectJohn Wiegley2010-06-121-11/+0
|
* Untabified all source filesJohn Wiegley2010-06-117-50/+50
|
* The --anon option now anonymizes commoditiesJohn Wiegley2010-06-091-3/+3
| | | | Fixes #227 / 1C90D8AF-830E-43C2-A5B7-D382F68EBDE3
* New display flag AMOUNT_PRINT_ELIDE_COMMODITY_QUOTESJohn Wiegley2010-06-091-6/+6
| | | | | | | | This is used by reports like register and balance so that separated commodities without spaces in them needed be surrounded by quotes. It will still occur in most other places. Fixes #200 / F82CF11F-BFD9-4512-A562-202B04B68051
* A further simplification of -V and -XJohn Wiegley2010-06-072-11/+11
| | | | | | | | With -X COMM, all values are computed in terms of COMM, regardless. With -V, only secondary commodities will ever be computed, never primaries. Further, if a secondary commodities has an associated price, the valuation is done in terms of that price's commodity.
* Fixed the way prices and costs are print'dJohn Wiegley2010-06-074-553/+553
|
* amount_t::print and value_t::print now use flagsJohn Wiegley2010-06-071-4/+4
|
* Added a 'speedtest' Makefile targetJohn Wiegley2010-06-071-0/+32717
|
* Reworked the way that <Rounding> entries are shownJohn Wiegley2010-06-062-3/+0
| | | | Fixes #188 / 53BCED29-F3B9-4E02-9A35-6C739ABB9662
* A little bit of code cleanupJohn Wiegley2010-06-041-7/+7
|
* Minor optimization of amount_t::operator*John Wiegley2010-06-031-6/+6
|
* Correct display of amounts with keep_precisionJohn Wiegley2010-06-022-1/+178
| | | | Fixes #167 / 1D275740-D1A6-42B7-BDE4-F2F85E30CE8E
* Remove redundant code in LedgerHarness.pyJohn Wiegley2010-06-021-2/+0
|
* Further improved parsing of query expressionsJohn Wiegley2010-06-011-4/+2
| | | | Fixes #210 / D4C2DD6F-8967-4FFC-BBBC-A941F9C53475
* Changed --european option to --decimal-commaJohn Wiegley2010-06-012-4/+4
| | | | Fixes #211 / 1736ACA5-5DE6-4826-AEB4-DB5B2A2217AC
* -G option now takes price history into accountJohn Wiegley2010-05-302-2/+4
|
* -V/-X options now take price history into accountJohn Wiegley2010-05-302-3/+4
|
* Empty notes and tags now return null valuesJohn Wiegley2010-05-301-2/+2
|
* Optimized amount_t::in_place_truncateJohn Wiegley2010-05-261-6/+6
|
* Added a new baseline test for the print commandJohn Wiegley2010-05-231-0/+11
|
* Added --rounding option, which is off by defaultJohn Wiegley2010-05-231-1/+1
| | | | | | | | The purpose of this option is to add special "<Rounding>" postings, to ensure that a regiter's running total is *always* the sum of its postings. Within --rounding, these adjustment postings are missing, which was the behavior in Ledger 2.x. It can be orders of magnitude slower to turn it on for large reports with many commodities.
* Do not implicitly sort register outputJohn Wiegley2010-03-176-55/+55
| | | | The switches the default back to the same as 2.x, which is --unsorted.
* Rewrite the "print" command as a custom functionJohn Wiegley2010-03-081-10/+0
| | | | | There ended up being too many corner cases for the generalized formatter to handle.
* Fixed tests relative to recent --pivot changeJohn Wiegley2010-02-046-28/+28
|
* Added baseline tests for unrealized optionsAristid Breitkreuz2009-11-253-0/+68
| | | | | This includes another baseline test for --unrealized, and also new ones for --unrealized-gains and --unrealized-losses.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-06 11:34:07 +0000