Add asset filter customization #56
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
styfle
reviewed
Jun 25, 2019
styfle
approved these changes
Jun 25, 2019
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows some new configuration options for asset filter customization:
filterAssetBasethe base path below which assets will never be emitted. This is necessary to fix a now-node bug.emitDirnameAll- a boolean option to determine whether it is possible to emit the entire contents of the local directory with just a free__dirnamereferenece.emitFilterAssetBaseAll- a boolean option to determine whether it is possible to emit the entire contents of thefilterAssetBaseby just referencing it.(2) and (3) could be left out of this PR possibly too.