both the quantity and the cost are zero. This is usually what you want, but if you do only want to check whether the quantity is zero, you can run mixedAmountStripPrices (or similar) before this. (multiply|divide)(Mixed)?Amount now also multiply or divide the TotalPrice if it is present, and the old (multiply|divide)(Mixed)?AmountAndPrice functions are removed.
		
			
				
	
	
		
			145 lines
		
	
	
		
			6.4 KiB
		
	
	
	
		
			Haskell
		
	
	
	
	
	
			
		
		
	
	
			145 lines
		
	
	
		
			6.4 KiB
		
	
	
	
		
			Haskell
		
	
	
	
	
	
| {-# LANGUAGE NamedFieldPuns #-}
 | |
| {-# LANGUAGE OverloadedStrings #-}
 | |
| {-# LANGUAGE ViewPatterns #-}
 | |
| {-# LANGUAGE CPP #-}
 | |
| {-|
 | |
| 
 | |
| A 'TransactionModifier' is a rule that modifies certain 'Transaction's,
 | |
| typically adding automated postings to them.
 | |
| 
 | |
| -}
 | |
| module Hledger.Data.TransactionModifier (
 | |
|    modifyTransactions
 | |
| )
 | |
| where
 | |
| 
 | |
| import Control.Applicative ((<|>))
 | |
| import Data.Maybe
 | |
| #if !(MIN_VERSION_base(4,11,0))
 | |
| import Data.Monoid ((<>))
 | |
| #endif
 | |
| import qualified Data.Text as T
 | |
| import Data.Time.Calendar
 | |
| import Hledger.Data.Types
 | |
| import Hledger.Data.Dates
 | |
| import Hledger.Data.Amount
 | |
| import Hledger.Data.Transaction
 | |
| import Hledger.Query
 | |
| import Hledger.Data.Posting (commentJoin, commentAddTag)
 | |
| import Hledger.Utils
 | |
| 
 | |
| -- $setup
 | |
| -- >>> :set -XOverloadedStrings
 | |
| -- >>> import Hledger.Data.Posting
 | |
| -- >>> import Hledger.Data.Transaction
 | |
| -- >>> import Hledger.Data.Journal
 | |
| 
 | |
| -- | Apply all the given transaction modifiers, in turn, to each transaction.
 | |
| -- Or if any of them fails to be parsed, return the first error. A reference
 | |
| -- date is provided to help interpret relative dates in transaction modifier
 | |
| -- queries.
 | |
| modifyTransactions :: Day -> [TransactionModifier] -> [Transaction] -> Either String [Transaction]
 | |
| modifyTransactions d tmods ts = do
 | |
|   fs <- mapM (transactionModifierToFunction d) tmods  -- convert modifiers to functions, or return a parse error
 | |
|   let
 | |
|     modifytxn t = t''
 | |
|       where
 | |
|         t' = foldr (flip (.)) id fs t  -- apply each function in turn
 | |
|         t'' = if t' == t  -- and add some tags if it was changed
 | |
|               then t'
 | |
|               else t'{tcomment=tcomment t' `commentAddTag` ("modified",""), ttags=("modified","") : ttags t'}
 | |
|   Right $ map modifytxn ts
 | |
| 
 | |
| -- | Converts a 'TransactionModifier' to a 'Transaction'-transforming function
 | |
| -- which applies the modification(s) specified by the TransactionModifier.
 | |
| -- Or, returns the error message there is a problem parsing the TransactionModifier's query.
 | |
| -- A reference date is provided to help interpret relative dates in the query.
 | |
| --
 | |
| -- The postings of the transformed transaction will reference it in the usual
 | |
| -- way (ie, 'txnTieKnot' is called).
 | |
| --
 | |
| -- Currently the only kind of modification possible is adding automated
 | |
| -- postings when certain other postings are present.
 | |
| --
 | |
| -- >>> t = nulltransaction{tpostings=["ping" `post` usd 1]}
 | |
| -- >>> import qualified Data.Text.IO as T
 | |
| -- >>> test = either putStr (T.putStr.showTransaction) . fmap ($ t) . transactionModifierToFunction nulldate
 | |
| -- >>> test $ TransactionModifier "" ["pong" `post` usd 2]
 | |
| -- 0000-01-01
 | |
| --     ping           $1.00
 | |
| --     pong           $2.00  ; generated-posting: =
 | |
| -- <BLANKLINE>
 | |
| -- >>> test $ TransactionModifier "miss" ["pong" `post` usd 2]
 | |
| -- 0000-01-01
 | |
| --     ping           $1.00
 | |
| -- <BLANKLINE>
 | |
| -- >>> test $ TransactionModifier "ping" ["pong" `post` amount{aismultiplier=True, aquantity=3}]
 | |
| -- 0000-01-01
 | |
| --     ping           $1.00
 | |
| --     pong           $3.00  ; generated-posting: = ping
 | |
| -- <BLANKLINE>
 | |
| --
 | |
| transactionModifierToFunction :: Day -> TransactionModifier -> Either String (Transaction -> Transaction)
 | |
| transactionModifierToFunction refdate TransactionModifier{tmquerytxt, tmpostingrules} = do
 | |
|   q <- simplifyQuery . fst <$> parseQuery refdate tmquerytxt
 | |
|   let
 | |
|     fs = map (tmPostingRuleToFunction tmquerytxt) tmpostingrules
 | |
|     generatePostings ps = [p' | p <- ps
 | |
|                               , p' <- if q `matchesPosting` p then p:[f p | f <- fs] else [p]]
 | |
|   Right $ \t@(tpostings -> ps) -> txnTieKnot t{tpostings=generatePostings ps}
 | |
| 
 | |
| -- | Converts a 'TransactionModifier''s posting rule to a 'Posting'-generating function,
 | |
| -- which will be used to make a new posting based on the old one (an "automated posting").
 | |
| -- The new posting's amount can optionally be the old posting's amount multiplied by a constant.
 | |
| -- If the old posting had a total-priced amount, the new posting's multiplied amount will be unit-priced.
 | |
| -- The new posting will have two tags added: a normal generated-posting: tag which also appears in the comment,
 | |
| -- and a hidden _generated-posting: tag which does not.
 | |
| -- The TransactionModifier's query text is also provided, and saved
 | |
| -- as the tags' value.
 | |
| tmPostingRuleToFunction :: T.Text -> TMPostingRule -> (Posting -> Posting)
 | |
| tmPostingRuleToFunction querytxt pr =
 | |
|   \p -> renderPostingCommentDates $ pr
 | |
|       { pdate    = pdate  pr <|> pdate  p
 | |
|       , pdate2   = pdate2 pr <|> pdate2 p
 | |
|       , pamount  = amount' p
 | |
|       , pcomment = pcomment pr `commentAddTag` ("generated-posting",qry)
 | |
|       , ptags    = ("generated-posting", qry) :
 | |
|                    ("_generated-posting",qry) :
 | |
|                    ptags pr
 | |
|       }
 | |
|   where
 | |
|     qry = "= " <> querytxt
 | |
|     amount' = case postingRuleMultiplier pr of
 | |
|         Nothing -> const $ pamount pr
 | |
|         Just n  -> \p ->
 | |
|           -- Multiply the old posting's amount by the posting rule's multiplier.
 | |
|           let
 | |
|             pramount = dbg6 "pramount" $ head $ amounts $ pamount pr
 | |
|             matchedamount = dbg6 "matchedamount" $ pamount p
 | |
|             -- Handle a matched amount with a total price carefully so as to keep the transaction balanced (#928).
 | |
|             -- Approach 1: convert to a unit price and increase the display precision slightly
 | |
|             -- Mixed as = dbg6 "multipliedamount" $ n `multiplyMixedAmount` mixedAmountTotalPriceToUnitPrice matchedamount
 | |
|             -- Approach 2: multiply the total price (keeping it positive) as well as the quantity
 | |
|             Mixed as = dbg6 "multipliedamount" $ n `multiplyMixedAmount` matchedamount
 | |
|           in
 | |
|             case acommodity pramount of
 | |
|               "" -> Mixed as
 | |
|               -- TODO multipliers with commodity symbols are not yet a documented feature.
 | |
|               -- For now: in addition to multiplying the quantity, it also replaces the
 | |
|               -- matched amount's commodity, display style, and price with those of the posting rule.
 | |
|               c  -> Mixed [a{acommodity = c, astyle = astyle pramount, aprice = aprice pramount} | a <- as]
 | |
| 
 | |
| postingRuleMultiplier :: TMPostingRule -> Maybe Quantity
 | |
| postingRuleMultiplier p =
 | |
|     case amounts $ pamount p of
 | |
|         [a] | aismultiplier a -> Just $ aquantity a
 | |
|         _                   -> Nothing
 | |
| 
 | |
| renderPostingCommentDates :: Posting -> Posting
 | |
| renderPostingCommentDates p = p { pcomment = comment' }
 | |
|     where
 | |
|         dates = T.concat $ catMaybes [showDate <$> pdate p, ("=" <>) . showDate <$> pdate2 p]
 | |
|         comment'
 | |
|             | T.null dates = pcomment p
 | |
|             | otherwise    = (wrap "[" "]" dates) `commentJoin` pcomment p
 |