Allow default tasks to be declared in the builder > customTasks section of the ui5.yaml
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 511
- Forks
- 83
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 55
Description
Expected Behavior
Allow to define default tasks such as generateManifestBundle or generateCachebusterInfo to be declared in the ui5.yamls builder > customTasks section - similar like a custom task.
Current Behavior
Right now, this can only be done for custom tasks. You can add a default task into the list of custom tasks and the build will not fail but it will also not include the default task into the execution.
Steps to reproduce the issue
n/a
Context
latest
Affected components (if known)
Log Output / Stack Trace
n/a
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.
Research direction
Start in the ui5-builder handling for the builder > customTasks section in ui5.yaml, focusing on how default tasks such as generateManifestBundle and generateCachebusterInfo are identified. Confirm that declaring a default task there includes it in the build execution, without breaking custom-task handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100