microsoftgraph / microsoftgraph/msgraph-metadata

Problems in current published v1.0 and beta metadata on 2020-09-21

Open
#31 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

promote
Dominant language
XSLT
Stars
166
Forks
55
Avg merge
16h 12m
Merged PRs (30d)
14

Description

When attempting to generate code from the current state of metadata from the service metadata urls on 2020-09-21, I found the following problems:

v1.0:

  • Entities without keys:
    microsoft.graph.policyRoot
    microsoft.graph.educationRoot
    microsoft.graph.cloudCommunications
    microsoft.graph.planner
    microsoft.graph.security
    microsoft.graph.appCatalogs
    microsoft.graph.teamwork
    microsoft.graph.informationProtection

beta:

  • Entities without keys:
    microsoft.graph.auditLogRoot
    microsoft.graph.policyRoot
    microsoft.graph.bitlocker
    microsoft.graph.compliance
    microsoft.graph.identityContainer
    microsoft.graph.trustFramework
    microsoft.graph.directory
    microsoft.graph.roleManagement
    microsoft.graph.educationRoot
    microsoft.graph.identityGovernance
    microsoft.graph.identityProtectionRoot
    microsoft.graph.officeConfiguration
    microsoft.graph.financials
    microsoft.graph.planner
    microsoft.graph.print
    microsoft.graph.security
    microsoft.graph.commsApplication
    microsoft.graph.external
    microsoft.graph.appCatalogs

The fix for all of these is to add the attribute BaseType="graph.entity" but of course that's for you guys to confirm. I notice that the current state of the metadata in this repository seems to have these issues fixed (I didn't check all of them). When will the new metadata be published?

BTW thanks for exposing this metadata repo! Just what I wanted (assuming that the Graph team address issues raised here!).

AB#7458

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the metadata returned by the service metadata URLs with the current metadata in the repository, focusing on the listed entities and their BaseType attributes. Confirm whether the published v1.0 and beta metadata still contain the reported missing keys; done means the corrected metadata is published or the publication status is documented.

Written by the indexing model from the issue text.

Assessment

Domain
api, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.