microsoftgraph / microsoftgraph/msgraph-metadata
Consider SDK generation process to start after a schema sync
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
SDK generation can consume CSDLs under schemas folder instead of syncing from $metadata:
https://github.com/microsoftgraph/msgraph-metadata/blob/ff6e8bcdf8a92282c134dfd3a3732fc0d371d2d9/schemas/v1.0-Prod.csdl
https://github.com/microsoftgraph/msgraph-metadata/blob/ff6e8bcdf8a92282c134dfd3a3732fc0d371d2d9/schemas/beta-Prod.csdl
That way, we have the potential to kick off the generation process on schema sync instead of weekly schedule, which can give us SDK release cadence that is aligned more with schema release cadence.
Potential tradeoff to consider is more frequent SDK PR reviews, but they could be reviewed faster if the schema changes are smaller.
related #175
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 schema inputs schemas/v1.0-Prod.csdl and schemas/beta-Prod.csdl, along with the current process that syncs from $metadata. Determine how SDK generation could consume those files after a schema sync rather than a weekly schedule. Done would mean generation is aligned with schema releases, with the tradeoff of more frequent SDK pull requests considered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100