This commit is contained in:
2020-01-23 00:56:03 +00:00
parent 23c0264127
commit 4dbb74764d
3 changed files with 13 additions and 1 deletions

View File

@@ -9,6 +9,9 @@ TODO: DataFilter how to distinguish between filtering on specific ID value or on
- Might need to add a filter on ID type of thing maybe?
- Wait and see...YAGNI scenario maybe
PagedResponse url is not including all the parameters like the datalisttype so technically it's invalid
- fix the url so it includes the full query string parameters that matter and are not paging related
INTEGRATION TEST UPDATE Update tests when appropriate (when it's working fully and not mocked)
UPDATE SPEC DOCS with new format and names etc or at least remove nonsense as necessary

View File

@@ -7,6 +7,8 @@ using AyaNova.Api.ControllerHelpers;
using AyaNova.Biz;
using AyaNova.DataList;
using System.Threading.Tasks;
using Newtonsoft.Json;
using Newtonsoft.Json.Linq;
namespace AyaNova.Api.Controllers
{
@@ -23,6 +25,7 @@ namespace AyaNova.Api.Controllers
private readonly ApiServerState serverState;
/// <summary>
/// ctor
/// </summary>

View File

@@ -81,6 +81,9 @@ namespace AyaNova
config.Filters.Add(new AyaNova.Api.ControllerHelpers.ApiCustomExceptionFilter(_newLog));
});
//Prevent default model binding automatic 400 page so we can consistently show *our* error to our specs
//https://docs.microsoft.com/en-us/aspnet/core/web-api/index?view=aspnetcore-3.1#automatic-http-400-responses
MvcBuilder.ConfigureApiBehaviorOptions(options =>
@@ -89,9 +92,12 @@ namespace AyaNova
});
_newLog.LogDebug("BOOT: init JSON");
MvcBuilder.AddNewtonsoftJson(options =>
{
options.SerializerSettings.Formatting = Newtonsoft.Json.Formatting.None;
options.SerializerSettings.DateTimeZoneHandling = Newtonsoft.Json.DateTimeZoneHandling.Utc;
});
@@ -134,7 +140,7 @@ namespace AyaNova
bool LOG_SENSITIVE_DATA = false;
#if (DEBUG)
LOG_SENSITIVE_DATA = false;
LOG_SENSITIVE_DATA = false;
#endif