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'm currently porting an addon to the V2 package format. During this I encountered an issue with the macro helpers.
Error: Attempted to resolve `macroCondition`, which was expected to be a helper, but nothing was found.
at resolveHelper (http://localhost:4200/assets/vendor.js:28257:15)
at encodeOp (http://localhost:4200/assets/vendor.js:30101:18)
at pushOp (http://localhost:4200/assets/vendor.js:30036:7)
at http://localhost:4200/assets/vendor.js:28458:7
at Compilers.compile (http://localhost:4200/assets/vendor.js:28443:7)
at expr (http://localhost:4200/assets/vendor.js:28601:19)
at http://localhost:4200/assets/vendor.js:28565:5
at Compilers.compile (http://localhost:4200/assets/vendor.js:28443:7)
at expr (http://localhost:4200/assets/vendor.js:28601:19)
at http://localhost:4200/assets/vendor.js:29821:7
It seems that when a consumer builds the app, helper macros are not being detected properly. Function based macros seem to work as intended.
Running the tests will reveal that the call macroCondition still exists in the template after build time. Inspecting the bundle of the function macro reveals that that one did get compiled away.
The text was updated successfully, but these errors were encountered:
I'm currently porting an addon to the V2 package format. During this I encountered an issue with the macro helpers.
It seems that when a consumer builds the app, helper macros are not being detected properly. Function based macros seem to work as intended.
I have a reproduction of the issue in the following repository:
https://github.com/SanderKnauff/v2-macro-repro
Running the tests will reveal that the call
macroCondition
still exists in the template after build time. Inspecting the bundle of the function macro reveals that that one did get compiled away.The text was updated successfully, but these errors were encountered: