microsoftgraph / microsoftgraph/msgraph-metadata
Organize XSLT based on scenario
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
We should organize our XSLT based on scenarios. This will mean have a primary XSLT (the existing one) and import the scenarios. Tentative scenarios:
-- metadataFix.xsl - where we inventory and add metadata to fix issues in the production metadata. This fix is temporary until it is fixed in the metadata.
-- toolingFix.xsl - where we inventory and alter metadata that works around issues in our generation tools. This fix is temporary until we fix the tools.
-- apiWorkaround.xsl - where we inventory and alter metadata that works around OData non-conformance.
https://github.com/microsoftgraph/msgraph-metadata/pull/33
AB#6327
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
Start by reviewing the existing primary XSLT and the referenced pull request #33. The issue proposes separating metadataFix.xsl, toolingFix.xsl, and apiWorkaround.xsl as imported scenarios; done means the primary transformation imports these scenario-specific files with their responsibilities separated.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100