Fix leading slash handling for flat format #760
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.
Handle leading slash for flat format when origin is not included in prefix or
prefix is non-existant
Prior behavior:
When a prefix is included in the Notification, a leading slash is emitted
However, when the Notification does not include a prefix and/or the origin is
excluded from the prefix Path, a leading slash is omitted
Behavior post fix:
Without origin population either in Notification prefix or Update