Suggest: add copy files options in schema
See original GitHub issueType of Issue
[ ] Bug Report
[x] Feature Request
Description
Copy README.md
file by default. But when have multiple language versions, like this:
README.md
README.zh-CN.md
I need to manually copy other language versions.
Sometimes, project need dependencies original styles files (like less
) in release package.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:74
- Comments:16 (1 by maintainers)
Top Results From Across the Web
Schema and data type mapping in copy activity - Microsoft Learn
This article describes how the Azure Data Factory copy activity perform schema mapping and data type mapping from source data to sink data....
Read more >COPY INTO <table> - Snowflake Documentation
COPY INTO <table>¶. Loads data from staged files to an existing table. The files must already be staged in one of the following...
Read more >COPY INTO | Databricks on AWS
Learn how to use the COPY INTO syntax of the Delta Lake SQL language in Databricks SQL and Databricks Runtime.
Read more >Specifying a schema | BigQuery - Google Cloud
Manually specifying schemas · Option 1: Use Add field and specify each field's name, type, and mode. · Option 2: Click Edit as...
Read more >COPY examples - Amazon Redshift - AWS Documentation
You can use a manifest to ensure that your COPY command loads all of the required files, and only the required files, from...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi there, earlier this week I realized that there is no copy functionality for library assets.
Therefore I have extended the @angular-devkit/build-ng-packagr:build and created an own one with asset copy functionality.
Here you will find how to use it: https://github.com/linnenschmidt/build-ng-packagr#how-to-use-it
Please give it a try. Maybe this approach is enough for you.
Hi @mario-d-s, thanks for you interest. I actually had a chat around this with @mgechev a couple of hrs ago.
We should be having more discussions around this in the near future. The first steps though would be to iron out the public api and the scope of the features, ie which scenarios will be supported and not supported.
“Copy and paste” of assets might probably be enough for most users, and probably will be the first iteration when this is included.