Issue by nex3Originally opened as dart-lang/sdk#19491
If a build error causes an asset not to be generated, rather than just deleting that asset from the graph barback should set it to an error state. The error should then be propagated down through all transformations of that asset, and should be exposed to the user if they call [getAsset] for a tainted asset.
Issue by nex3 Originally opened as dart-lang/sdk#19491
If a build error causes an asset not to be generated, rather than just deleting that asset from the graph barback should set it to an error state. The error should then be propagated down through all transformations of that asset, and should be exposed to the user if they call [getAsset] for a tainted asset.