From a trialing user (Discord, 2026-08-11). Today, A|B in the aisle config only affects shopping-list grouping. The user expected B to act as a workspace-wide alias for A — across ingredients, search, shopping list, and pantry.
Their motivating example:
Bell Peppers and Capsicum are just 2 different names for the same item, used in different regions of the world. Say you're importing a recipe from India or Australia, you would see Capsicum. But you wouldn't want that to be any different from Bell Pepper.
For example for commands like cook pantry recipes... You wouldn't want to think you don't have the items only to realise you had them, just under a different name.
So: aisle aliases should be resolved wherever ingredient names are matched — pantry matching (pantry recipes), search, shopping-list merging — not only when grouping the shopping list by aisle.
Related: #417 notes the two Context implementations diverge on aisle/pantry fallback, which would matter for wherever this resolution lives.
From a trialing user (Discord, 2026-08-11). Today,
A|Bin the aisle config only affects shopping-list grouping. The user expectedBto act as a workspace-wide alias forA— across ingredients, search, shopping list, and pantry.Their motivating example:
So: aisle aliases should be resolved wherever ingredient names are matched — pantry matching (
pantry recipes), search, shopping-list merging — not only when grouping the shopping list by aisle.Related: #417 notes the two Context implementations diverge on aisle/pantry fallback, which would matter for wherever this resolution lives.