Name `Microsoft.Graph.Security` Collision Between Namespace and Class FQN
fey101 opened this issue · comments
Issue detected in pipeline run here.
Error: error CS0101: The namespace 'Microsoft.Graph' already contains a definition for 'Security'
Need to refactor the generator to make it possible for the namespace and class to co-exist without raising compilation error.
Workload owner Confirmed the intentionality of the above as follows:
"
The microsoft.graph.security singleton in Prod (beta & v1.0) exists for few years. It does not exists in PPE. I added it to my workload in PPE in order to mimic the same behavior as in Prod. We've been requested to move all our entities (in M365Defender workload) to a new sub namespace - microsoft.graph.security. We moved all our entities to the new sub namespace, but we didn't touch the security singleton in order to mimic the behavior in Prod
"
@fey101 Is it the same functionality in the m.g.security entity as in the m.g.security namespace?
@fey101 Is it the same functionality in the m.g.security entity as in the m.g.security namespace?
@MIchaelMainer I believe that would be correct. It seems that the existing entity (m.g.security) is being enriched with property types from the new m.g.security namespace according to the staging metadata.
