Azure / Azure/bicep-extensibility
Design for improvements to passing import config between modules
Open
story: extensibility
- Dominant language
- C#
- Stars
- 19
- Forks
- 15
- Avg merge
- 3h 11m
- Merged PRs (30d)
- 20
Description
It's very verbose to have to redeclare the `import` statement in every file and manually pass parameters down for configuration.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points; start by mapping how import statements and configuration parameters are passed between modules in the service-side implementation. Done would require an agreed design for reducing repeated imports and manual parameter passing, followed by implementation scope and validation criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100