Unblock PowerShell Generation in the Calendar Module #3330
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merge to Main
Merge dev to main
…powershell into merge-to-main-20-11-2024
Merge changes latest updates to main
…owershell into merge-to-live-24-02-2025
…powershell into merge-to-main-16-04-2025
Merge to main 16 04 2025
…powershell into merge-to-main-09-05-2025
ramsessanchez
changed the title
ramsessanchez
changed the title
|
To be clear....
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding two regex expressions to the Directives list which will remove paths from generation based on Operation Id matches:
.exceptionOccurrence.$|
.instance(_|.).$|
Anything with
exceptionOccurrencein the operation id, this is becauseexceptionOccurrenceshouldn't exist in the URI path at all as it is a navigation property.Anything where the operation id includes
path .instance.or.instance_. This is because instance shouldn't be followed by path segment in the URI, instead it should always be followed by a datetime window query according to documentation.instance_implies that the URI has the followinginstance/{event-id}/which we know isn't allowed since instance needs to be at the end and followed by a date time window query.