Skip to content

v0.0.3

Latest

Choose a tag to compare

@lhelwerd lhelwerd released this 15 May 21:16

0.0.3 - 2026-05-15

Changed

  • Display which products are being updated and deleted when a change to the
    products inventory is detected at the start of the new subcommand.
  • Allow product metadata range to be created or updated when the parent generic
    product or sibling range products match, but only when the range product also
    matches but is simply overshadowed by its siblings.
  • Allow product metadata review and edit after all receipt products are matched
    and the --more argument was not used for the new subcommand.
  • Indicate if pending product metadata that is not matching any products on the
    receipt and is thus going to be lost after an edit, match or write in the
    new subcommand, using YAML format.
  • Allow product metadata price matchers to only match product items on receipts
    from a specific year and month combination, by formatting the year and month
    in the indicator with a dash in between.
  • Allow product metadata label and discount matchers to contain regular
    expressions starting with a caret (^) which matches product items no other
    metadata matches.
  • Allow product metadata to match when it has just one of the price matchers
    with minimum/maximum interval end indicators, making it match all receipt
    products with prices from or until the bound, respectively.
  • Merge product metadata with price matchers with and without indicators by
    turning a price without indicator into one with indicators based on the other
    product's indicators and combining minimum/maximum intervals.

Fixed

  • Avoid committing modifications to the database when an exception occurs, and
    instead rollback any transactions.
  • Correct saving products to database when they are based on an existing product
    and then edited in new subcommand, including when a range product is edited.
  • Edited existing products are no longer lost during matching to receipt items
    due to overshadows of existing products in new subcommand.
  • Do not lose changes to existing product metadata in new subcommand.
  • Do not lose pending product metadata where a range product matches after edit
    of receipt in new subcommand.
  • Do not lose pending product metadata after edit of multiple products in new
    subcommand.
  • Avoid using a range product metadata for augmentation if we initially
    indicate we select the generic product.
  • Avoid conflict with existing product metadata when splitting range products
  • Create directories when writing receipt/metadata files in new subcommand.
  • Correct spaces between options in meta prompt of new subcommand.
  • Update suggestions for indicators and prices from products added to the
    receipt for meta step of new subcommand.