dart-lang / native / 11215711141 / 7 – native_assets_cli_ubuntu
27%
main: 27%

DEFAULT BRANCH: main
Ran
Files 35
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 85.432%. Remained the same
native_assets_cli_ubuntu – 11215711141.7

push

github

web-flow 
Ensure the NativeAssetsBuildRunner.link() produces a BuildResult with all assets (#1633)

* Ensure the NativeAssetsBuildRunner.link() produces a BuildResult with all assets

Before this change a bundling tool would

  * call `buildResult = nativeAssetsBuildRunner.build(...)`
  * call `linkResult = nativeAssetsBuildRunner.link(buildResult: buildResult, ...)
  * get all assets via `allAssets = [...buildResult.assets, ...linkResult.assets]`

=> This PR makes the `link()` command produce a `LinkResult` containing
   all assets of the final application.

=> One could view this as the assets from `build()` without a linker to go to
   a default linker that just emits all of it's inputs.

=> This allows the `link()` step to also perform the application-wide
   validation steps (not just over all linker outputs but across build &
   link outputs)

Bundling tools now only have to deal with
  * `buildResult` in JIT mode (where linking is not enabled)
  * `linkResult` in AOT mode (where linking is enabled)

Instead of dealing with both `buildResult` and `linkResult` in AOT mode.

(In some sense one actually would prefer a `NativeAssetsBuilder.build` and
`NativeAssetsBuilder.buildAndLink` instead of the current API that exposes the
intermediary result from `build(linkingEnabled: true)` just to be explicitly
passed on to link later on)

950 of 1112 relevant lines covered (85.43%)

8.56 hits per line

Source Files on job native_assets_cli_ubuntu - 11215711141.7