| | | 1 | | using ArturRios.Mediator.Command; |
| | | 2 | | |
| | | 3 | | namespace ArturRios.Heimdall.Command.Output; |
| | | 4 | | |
| | | 5 | | /// <summary> |
| | | 6 | | /// Result of <see cref="Input.DeleteGoogleUserCommand" /> (UC-28). Reports the Google User's |
| | | 7 | | /// <c>PublicId</c> and whether the request was the idempotent no-op of AF-28b. Internal Ids never |
| | | 8 | | /// leave the data layer. |
| | | 9 | | /// </summary> |
| | | 10 | | public class DeleteGoogleUserCommandOutput : CommandOutput |
| | | 11 | | { |
| | | 12 | | /// <summary>Public identifier of the deleted Google User.</summary> |
| | 25 | 13 | | public Guid Id { get; set; } |
| | | 14 | | |
| | | 15 | | /// <summary> |
| | | 16 | | /// <c>true</c> when the Google User was already logically deleted and nothing was written |
| | | 17 | | /// (AF-28b); <c>false</c> when this request performed the deletion. AF-28b answers with the |
| | | 18 | | /// same status and message as the main flow — the specification requires it to — so this flag |
| | | 19 | | /// is what tells them apart. |
| | | 20 | | /// </summary> |
| | 22 | 21 | | public bool AlreadyDeleted { get; set; } |
| | | 22 | | } |