Add error handling and update history query logic

- Introduced a using directive for exceptions in DocumentCreateReadSQL.cs.
- Enhanced CreateParmas method with try-catch for base64 conversion errors, throwing BadRequestException on failure.
- Added switch statement in HistoryController.cs to manage Related property in ReadHistoryQuery, setting flags for receiver and sender.
This commit is contained in:
Developer 02 2025-05-12 10:04:33 +02:00
parent 8b1199bc71
commit 9b945ce232
2 changed files with 13 additions and 7 deletions

View File

@ -1,5 +1,6 @@
using Dapper;
using EnvelopeGenerator.Application.Contracts.SQLExecutor;
using EnvelopeGenerator.Application.Exceptions;
using EnvelopeGenerator.Domain.Entities;
namespace EnvelopeGenerator.Application.SQL;
@ -33,10 +34,17 @@ public class DocumentCreateReadSQL : ISQL<EnvelopeDocument>
/// <param name="base64"></param>
/// <returns></returns>
public static DynamicParameters CreateParmas(string base64)
{
try
{
var parameters = new DynamicParameters();
byte[] byteData = Convert.FromBase64String(base64);
parameters.Add("ByteData", byteData, System.Data.DbType.Binary);
return parameters;
}
catch(FormatException ex)
{
throw new BadRequestException(ex.Message.Replace("input", "dataAsBase64"));
}
}
}

View File

@ -110,8 +110,6 @@ public class HistoryController : ControllerBase
bool withReceiver = false;
bool withSender = false;
switch (history.Related)
{
case ReferenceType.Receiver: