-
-
Notifications
You must be signed in to change notification settings - Fork 549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automation not running on first ingredient #2927
Comments
That is strange, will take a look, should probably also add a test not only for the individual parts but also some. Examples like this one |
Spun up a new instance: it works. On my production instance: still no luck. |
Are there other automations on pasta? |
Pasta was just a simplified example after I noticed that a more complex automation didn't affect a first ingredient of a recipe. Here's one that shouldn't interfere with anything else.
Same result whether the order parameter is 100 or 9000. Edit: I now also tested other types of automations (Food Alias, Unit Replace, Transpose Words), they all work as expected. Only Food Replace still shows the described behavior. |
Tandoor Version
1.5.12
Setup
Docker / Docker-Compose
Reverse Proxy
SWAG
Other
No response
Bug description
A
food replace
automation (and possibly other types too) doesn't get applied to the first food in a recipe's ingredient list.Steps to reproduce:
food replace
automation withparameter 1 = .*
,parameter 2 = pasta
,parameter 3 = potatoes
,order=1
result:
Pasta has been replaced in all occasions except the first.
Relevant logs
No response
The text was updated successfully, but these errors were encountered: