Support for custom CLI parameters
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 511
- Forks
- 83
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 55
Description
Is your feature request related to a problem? Please describe.
When I need to run e.g. ui5 serve with different configurations, I am currently forced to create multiple ui5*.yaml files. In some cases, I need exactly the same configuration except one value is different. The overhead of maintaining multiple files for that is increasing the costs of maintaining a UI5 project.
Describe the solution you'd like
Allow the usage of custom CLI parameters that are accessible in my middleware/task e.g. I would like to call ui5 serve --debug --magic 42 and in my middleware I have access to e.g. this global configuration as e.g. object
{
debug: true
magic: '42'
}
Describe alternatives you've considered
I could also solve the same problem, if it would also be possible to provide the configuration not as yaml but as js file. Then, I have all the flexibility needed to create inheritance between configs or custom creation of the config based on other parameters.
Additional context
No
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 with the ui5 serve command and trace how middleware and tasks receive configuration. Define how custom parameters such as --debug and --magic 42 should be exposed, then verify that the same configuration can be consumed without maintaining multiple ui5 YAML files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100