Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[s3-assets] some fields in AssetOptions are deprecated, but is that intended?

See original GitHub issue

The exclude and follow fields in AssetOptions interface were marked deprecated, because of #7708. But the pull doesn’t seem to have the intension to deprecate them. If not, they should be fixed.

This is a 📕 documentation issue

Issue Analytics

State:
Created 3 years ago
Comments:11 (6 by maintainers)

Top GitHub Comments

8reactions

danielsharveycommented, Nov 3, 2020

Should this be re-opened? The deprecation notice remains confusing…

3reactions

acomagucommented, Aug 23, 2020

From user perspective, they think that they should not use exclude field any more because it’s marked as deprecated. But actually no plan to remove the field from AssetOptions and we don’t need to worry about using it.

Top Results From Across the Web

interface AssetOptions · AWS CDK

Python, aws_cdk.aws_s3_assets.AssetOptions. TypeScript (source), @aws-cdk/aws-s3-assets » AssetOptions ... Deprecated: see assetHash and assetHashType.

@aws-cdk/aws-s3-assets | Yarn - Package Manager

Assets are local files or directories which are needed by a CDK app. A common example is a directory which contains the handler...

awscdk - Go Packages

AWS Cloud Development Kit Library. The AWS CDK construct library provides APIs to define your CDK application and add CDK constructs to the...

How should files for AWS AssetCode be excluded now?

Nothing you need to do, looks like there is an effort to move assets classes to core. The aws-lambda package uses aws-s3-assets AssetOptions...