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
I use the 'fn' helper to be able to add more positional arguments
😕 Actual Behavior
This renders [object Object]
<EmbeddedPrinterComponent @printer={{printer}} as |e|>
{{e.resourceExtruderCurrentTemperature true}}
</EmbeddedPrinterComponent>
🤔 Expected Behavior
Should render 3.5
<EmbeddedPrinterComponent @printer={{printer}} as |e|>
{{e.resourceExtruderCurrentTemperature true}}
</EmbeddedPrinterComponent>
🌍 Environment
ember-cli: 5.4.0
node: 18.18.0
os: darwin arm64
browser: chrome
➕ Additional Context
Using the let helper does render the expected output.
<EmbeddedPrinterComponent @printer={{printer}} as |e|>
{{#let (e.resourceExtruderCurrentTemperature true) as |value|}}{{value}}{{/let}}
</EmbeddedPrinterComponent>
@NullVoxPopuli suggested this might be a bug in 'fn', hence this report.
The text was updated successfully, but these errors were encountered:
Here is a reproduction, showing that this happens with Resources... but even worse: errors with Classic Class and function helpers. With the classic constructs, we get an error saying that call isn't a function, which leads me to believe that we never implemented native helper-manager aware partial application, and only used JavaScript's built in .call behavior.
My hypothesis is that the helper and Helper from @ember/component/helper aren't compatible with fn because neither are functions.
🐞 Describe the Bug
A yielded 'fn' from a component is incorrectly rendered as [object Object]
🔬 Minimal Reproduction
Inside a component I have this
I use the 'fn' helper to be able to add more positional arguments
😕 Actual Behavior
This renders
[object Object]
🤔 Expected Behavior
Should render
3.5
🌍 Environment
ember-cli: 5.4.0
node: 18.18.0
os: darwin arm64
browser: chrome
➕ Additional Context
Using the let helper does render the expected output.
@NullVoxPopuli suggested this might be a bug in 'fn', hence this report.
The text was updated successfully, but these errors were encountered: