Asset copy with wildcard in the input path
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- angular, typescript
- Domain
- build-system, cli
Research direction
Start by tracing asset handling in the build, serve, test, and e2e commands, since the issue reports different behavior across them. Define how wildcard input paths should establish the copy root and verify that the requested assets are copied without unwanted intermediate folders. Done means the wildcard path works consistently for the listed commands, including serve output.
Written by the indexing model from the issue text.
Description
🚀 Feature request
Command (mark with an x)
- [ ] new
- [ x] build
- [ x] serve
- [x ] test
- [ x] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
Description
Currently assets array allows glob with input path, however input path itself does not support wildcards.
Like ./node_modules/@myscope/**/assets/i18n/*
Where ** is any number of unknown libraries (like shared, services, featureabc).
With glob it would also create every folder between @myscope to assets/i18n, instead of copying just the contents of i18n.
Describe the solution you'd like
The input path allows wildcards to set the root or a flag to only copy contents of the glob result path.
Describe alternatives you've considered
Node scripts that requires extra steps and wouldn't know if project output is different from dist and it does not work with serve.
- Dominant language
- TypeScript
- Stars
- 27k
- Forks
- 11.8k
- Avg merge
- 17h 25m
- Merged PRs (30d)
- 183
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from angular/angular-cli
-
area: @angular/build gemini-triaged
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
angular/angular-cli#33955 ·
-
area: @angular/cli gemini-triaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
angular/angular-cli#33055 · 1 comment · 3 reactions ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34131 · 1 assignee ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34130 · 1 assignee ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34128 · 1 assignee ·
All issues in angular/angular-cli
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100