dsccommunity / dsccommunity/CommonTasks
All composite resources should be sorted in namespaces
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- PowerShell
- Stars
- 45
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
As the number of composite resources is getting larger, grouping them into namespaces is required
- ADDomainController
- WindowsComputerSettings
- ConfigurationBase
- DnsServerSettings
- DscTagging
- DscLcmMaintenanceWindows
- DscLcmController
- WindowsFilesAndFolders
- WindowsNetwork
- WindowsNetworkIpConfiguration
- WindowsRegistryValues
- SecurityBase
- WebApplicationPools
- WebApplications
- WebSites
- WebVirtualDirectories
- WindowsSoftwarePackages
- WindowsEventLogs
- WindowsFeatures
- WindowsServices
- XmlContent
@nyanhp, does this scale and do the prefixes make sense?
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
No files, tests, or entry points are named. Start by reviewing the repository’s composite-resource layout and any existing namespace conventions, then determine how the listed resources should be grouped and named. Done means all composite resources follow a consistent namespace scheme without unresolved prefix decisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100