You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now as I'm experimenting, it looks like if aliases are used, the alias is used everywhere in the human and web output, and the real name is unused. I'm not sure what the primary use case for aliases is, but I've been using it to be specific in the ingredient list but have a short name. For example, @small onion|onion{1*}(chopped). I want the step to show onion, but the ingredient list to show small onion.
Locally I was able to quickly emulate this behavior in the CLI by using .name instead of display_name() at the relevant point in the code, but I'm not sure if this is behavior that is useful to anyone else. Perhaps having a configuration setting or extension might be helpful? I'm more than happy to code something up if this is something you'd like.
The text was updated successfully, but these errors were encountered:
There I explain the design reasoning for why it works this way. I'll leave this open here as well to maybe, if more people ask, add a configuration setting to chef to change the behavior, but for now I'm hesitant.
Right now as I'm experimenting, it looks like if aliases are used, the alias is used everywhere in the human and web output, and the real name is unused. I'm not sure what the primary use case for aliases is, but I've been using it to be specific in the ingredient list but have a short name. For example,
@small onion|onion{1*}(chopped)
. I want the step to showonion
, but the ingredient list to showsmall onion
.Locally I was able to quickly emulate this behavior in the CLI by using
.name
instead ofdisplay_name()
at the relevant point in the code, but I'm not sure if this is behavior that is useful to anyone else. Perhaps having a configuration setting or extension might be helpful? I'm more than happy to code something up if this is something you'd like.The text was updated successfully, but these errors were encountered: