microsoftgraph / microsoftgraph/msgraph-metadata
Organize transforms to support different metadata consumers
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
We will need to support requet builders, PowerShell, model-only scenarios for generation. Each scenario has different requirements. We need to support transforms for each scenario. We want to have a base transform and then primary transforms for each scenario that imports the base transforms.
https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/89
AB#7453
Contributor guide
No contributing guide indexed for this repository
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 existing metadata transform organization and the linked PowerShell issue, then determine how request-builder, PowerShell, and model-only consumers differ. Done means a reusable base transform exists with primary transforms for each stated scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100