;changelogs
This commit is contained in:
		
							parent
							
								
									cd72070871
								
							
						
					
					
						commit
						df92c36679
					
				| @ -1,7 +1,10 @@ | ||||
| General/project-related changes in the hledger project.  | ||||
| For package-specific changes, see the package changelogs. | ||||
| 
 | ||||
| # 3178a860 | ||||
| # cd720708 | ||||
| 
 | ||||
| - add an example of Ledger's cap gains calculation during balancing | ||||
| 
 | ||||
| 
 | ||||
| - make ghcid-web-run | ||||
| 
 | ||||
|  | ||||
| @ -1,7 +1,9 @@ | ||||
| Internal/api/developer-ish changes in the hledger-lib (and hledger) packages. | ||||
| For user-visible changes, see the hledger package changelog. | ||||
| 
 | ||||
| # 3cc79a67 | ||||
| # 784d882e | ||||
| 
 | ||||
| - fixedlotpricep renamed to lotpricep, now also parses non-fixed lot prices | ||||
| 
 | ||||
| - Fix Documentation for journalExpenseAccountQuery (Pavan Rikhi) | ||||
| 
 | ||||
|  | ||||
| @ -1,7 +1,9 @@ | ||||
| User-visible changes in hledger-ui. | ||||
| See also the hledger changelog. | ||||
| 
 | ||||
| # 293e2d81 | ||||
| # 898cda4e | ||||
| 
 | ||||
| 
 | ||||
| 
 | ||||
| 
 | ||||
| 
 | ||||
|  | ||||
| @ -1,7 +1,9 @@ | ||||
| User-visible changes in hledger-web. | ||||
| See also the hledger changelog. | ||||
| 
 | ||||
| # 23a79af1 | ||||
| # 898cda4e | ||||
| 
 | ||||
| 
 | ||||
| 
 | ||||
| - web: add form: always start with four rows when opened | ||||
| 
 | ||||
|  | ||||
| @ -1,27 +1,37 @@ | ||||
| User-visible changes in the hledger command line tool and library. | ||||
| 
 | ||||
| 
 | ||||
| # e7e9f1ee | ||||
| # a016a437 | ||||
| 
 | ||||
| - Improved parse compatibility for Ledger lot prices: | ||||
|   hledger up to 1.17.1 did not accept Ledger's lot price syntax except | ||||
|   in vary limited circumstances (`{= }` at the end of the posting line). | ||||
|   hledger now accepts all four of Ledger's lot price syntaxes  | ||||
|   (`{PRICE}`, `{{PRICE}}`, `{=PRICE}`, `{{=PRICE}}`), | ||||
|   anywhere after the posting amount but before any balance assertion. | ||||
|   All of these lot prices are ignored. | ||||
| - cli: don't let an upper case file extension confuse file format | ||||
|   detection. (#1225) | ||||
| 
 | ||||
| - csv: don't discard explicit assignments of a 0 amount | ||||
|   Eg: an `amount1  $0.00` assignment was generating a posting1 with | ||||
|   missing amount. | ||||
| - cli: in the commands list, fix hiding of redundant source scripts | ||||
|   when a corresponding .com/.exe file exists. (#1225) | ||||
| 
 | ||||
| - cli, journal: period expressions now support "until" as a synonym | ||||
|   for "to", like Ledger. | ||||
| 
 | ||||
| - allow spaces between sign and number when parsing amounts | ||||
| 
 | ||||
| - csv: when both `amount` and `amountN`s are assigned, instead of | ||||
|   failing, just ignore `amount` and let the `amountN`s have | ||||
|   precedence. This makes it easier to override old `amount` rules. | ||||
| - journal: We now accept (but ignore) Ledger-style lot dates | ||||
|   (`[DATE]`) and four lot price forms (`{PRICE}`, `{{PRICE}}`, | ||||
|   `{=PRICE}`, `{{=PRICE}}`), anywhere after the posting amount but | ||||
|   before any balance assertion. | ||||
| 
 | ||||
| - csv: clarified the "too many non-zero amounts" error message. | ||||
| - journal: we now accept Ledger-style parenthesised "virtual posting | ||||
|   costs" (`(@)`, `(@@)`). In hledger these do the same as the | ||||
|   unparenthesised form. | ||||
| 
 | ||||
| - csv: allow generation of postings with an explicit 0 amount. (#1112) | ||||
| 
 | ||||
| - csv: for each posting, when both numbered and unnumbered amount | ||||
|   assignments are active, ignore the unnumbered ones. This makes it | ||||
|   easier to override old `amount` rules.  | ||||
|    | ||||
| - csv: fix a 1.17.1 regression involving amount-in/amount-out. (#1226) | ||||
| 
 | ||||
| - csv: improved the "too many non-zero amounts" error message. | ||||
| 
 | ||||
| # 1.17.1.1 2020-03-19 | ||||
| 
 | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user