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
When you generate an addon using the module unification layout but with the dummy app inside the test folder in "classic" mode, isModuleUnification check thinks the app is un MU layout, and doesn't reexport the contents of the addon's /src into /app automatically.
I think a more applicable approach for testing is what @mansona has done in https://github.com/mansona/testing-mu where you have in-repo apps that will serve as test apps. I think the blueprint for a mu addon should contain two apps by default: one classic, one mu-app to test the addon in both locations.
The logic in #7490 has a hole.
When you generate an addon using the module unification layout but with the dummy app inside the test folder in "classic" mode,
isModuleUnification
check thinks the app is un MU layout, and doesn't reexport the contents of the addon's/src
into/app
automatically.Reproduction: https://github.com/cibernox/my-mu-addon
The text was updated successfully, but these errors were encountered: