-
-
Notifications
You must be signed in to change notification settings - Fork 835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.x] [extensibility] Export all missing modules in compat #4044
Conversation
@DavideIadeluca for 2.x you don't actually need to do anything 👍 In 2.x every module used by the code (core and extensions) is accessible by other extensions. Unless the module is declared but not used (which is not the case currently). |
@SychO9 Yeah I was also of the same understanding per the diary you shared on discuss. But I'm kind of confused now what the usage is for the newly added framework/framework/core/js/src/forum/forum.ts Lines 1 to 53 in da441c7
framework/extensions/flags/js/src/forum/forum.ts Lines 1 to 10 in da441c7
|
@DavideIadeluca those are mostly the result of automatically converting the old compat files. A lot of the imports there are redundant and add nothing. However because we now lazy load certain components, those files serve as a way to ensure certain components are not lazy loaded, without having to constantly check where they are used. We'll probably remove those (forum.ts, common.ts, admin.ts) files for the bundled extensions before 2.0 is out. |
4d6f61b
to
68897d0
Compare
Fixes #4006 (comment)
Changes proposed in this pull request:
Reviewers should focus on:
Screenshot
QA
fireDebugWarning
)fireDeprecationWarning
)Necessity
Confirmed
composer test
).Required changes: