-
Notifications
You must be signed in to change notification settings - Fork 221
Adding support for DDC's Library Bundle module system. #4303
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
base: master
Are you sure you want to change the base?
Conversation
Package publishing
Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation. |
PR HealthChangelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs. This check can be disabled by tagging the PR with |
davidmorgan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
| bool emitDebugSymbols, | ||
| bool canaryFeatures, | ||
| bool ddcModules, | ||
| bool ddcLibraryBundle, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Optional, entirely up to you: this many adjacent positional bools makes me nervous, how about switching them to named?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please! I'd love to get to a place where we only use positional arguments for simple functions with one or two parameters and then default to using required named everywhere else, but obviously we don't have to do this all at once 😄
| ); | ||
| }); | ||
| }); | ||
| group('regression tests', () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super nitpicky optional nitpick: blank line here to give the group a bit of breathing space? :)
| @@ -1,3 +1,7 @@ | |||
| ## 5.1.5 | |||
|
|
|||
| - Adding support for DDC's Library Bundle module system. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use the direct form, "Add support for ...", or just "Support DDC's ..." would also work.
| @@ -1,5 +1,7 @@ | |||
| ## 4.4.6 | |||
| ## 4.4.7 | |||
| - Adding support for DDC's Library Bundle module system. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use the direct form "Add support for DDC's ..." or just "Support DDC's ...".
Not sure if this is a complete change or part of the work? If it's complete then maybe it's worth saying a bit more about the feature from the user's point of view, if you don't plan to release then the version should be 4.4.7-wip please :)
bkonyi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
| bool emitDebugSymbols, | ||
| bool canaryFeatures, | ||
| bool ddcModules, | ||
| bool ddcLibraryBundle, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please! I'd love to get to a place where we only use positional arguments for simple functions with one or two parameters and then default to using required named everywhere else, but obviously we don't have to do this all at once 😄
| /// Whether or not to emit DDC entrypoints that support web hot reload. | ||
| /// | ||
| /// Web hot reload is only supported for DDC's Library Bundle module system. | ||
| /// Only supported for DDC's Library Bundle module system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have any checks to enforce this? Or does useWebHotReload == true just do nothing if we're not using the new module system?
This module system - in conjunction with the Frontend Server - supports web hot reload. This is part of an effort to deprecate DDC's older module systems.
Notable updates:
ddc-library-bundleflag through several builders.webHotReloadand the new module system. These should be consistent now.