Fix CloudCommunications module generation by resolving circular reference #3482
+1
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AutoREST generation was failing silently for CloudCommunications module due to circular reference between
MicrosoftGraphEngagementConversationMessageandMicrosoftGraphEngagementConversation, preventing the module from being published in v2.33.0 and v2.34.0.Changes
MicrosoftGraphEngagementConversationMessageto theno-inlinedirective list insrc/readme.graph.mdThis breaks the circular dependency by instructing AutoREST to not inline the
MicrosoftGraphEngagementConversationMessagemodel during code generation, allowing the CloudCommunications module to build successfully.Original prompt
This section details on the original issue you should resolve
<issue_title>Microsoft.Graph.CloudCommunications not available in v2.33.0 or v2.34.0</issue_title>
<issue_description>### Describe the bug
For some reason, the Microsoft.Graph.CloudCommunications is missing from the last two releases. The Microsoft.Graph.Beta.CloudCommunications module is also out of sync with the rest of the Beta release: