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
Currently {{service "unknown-service"}} throws an assertion during render.
Users may want to check, whether a service exists. For this we could either add a second helper, e.g. {{service-exists "unknown-service"}} that returns true / false, or we could add an optional named parameter {{service "unknown-service" throwIfUnknown=false}} and return undefined, if the service is unknown.
I'm not yet convinced that this is a good idea and I did not have the need for it yet. Maybe this kind of logic should be kept in JS.
Looking for opinions / suggestions!
The text was updated successfully, but these errors were encountered:
Currently
{{service "unknown-service"}}
throws an assertion during render.Users may want to check, whether a service exists. For this we could either add a second helper, e.g.
{{service-exists "unknown-service"}}
that returnstrue
/false
, or we could add an optional named parameter{{service "unknown-service" throwIfUnknown=false}}
and returnundefined
, if the service is unknown.I'm not yet convinced that this is a good idea and I did not have the need for it yet. Maybe this kind of logic should be kept in JS.
Looking for opinions / suggestions!
The text was updated successfully, but these errors were encountered: