From 480691d3eddcf66b4cd4761180576a0bd5564e56 Mon Sep 17 00:00:00 2001 From: Attila Hajdrik Date: Tue, 8 May 2018 09:09:44 -0700 Subject: [PATCH] Convert the member names to camelCase for interfaces/class/types getting marshalled to C# side. --- .../src/Rendering/BrowserRenderer.ts | 8 ++++---- .../src/Services/Http.ts | 10 +++++----- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/src/Microsoft.AspNetCore.Blazor.Browser.JS/src/Rendering/BrowserRenderer.ts b/src/Microsoft.AspNetCore.Blazor.Browser.JS/src/Rendering/BrowserRenderer.ts index 10f382b4f9..e84a67d528 100644 --- a/src/Microsoft.AspNetCore.Blazor.Browser.JS/src/Rendering/BrowserRenderer.ts +++ b/src/Microsoft.AspNetCore.Blazor.Browser.JS/src/Rendering/BrowserRenderer.ts @@ -318,10 +318,10 @@ function raiseEvent(event: Event, browserRendererId: number, componentId: number } const eventDescriptor = { - BrowserRendererId: browserRendererId, - ComponentId: componentId, - EventHandlerId: eventHandlerId, - EventArgsType: eventArgs.type + browserRendererId, + componentId, + eventHandlerId, + eventArgsType: eventArgs.type }; platform.callMethod(raiseEventMethod, null, [ diff --git a/src/Microsoft.AspNetCore.Blazor.Browser.JS/src/Services/Http.ts b/src/Microsoft.AspNetCore.Blazor.Browser.JS/src/Services/Http.ts index a0a1cd5f46..f9e950c61f 100644 --- a/src/Microsoft.AspNetCore.Blazor.Browser.JS/src/Services/Http.ts +++ b/src/Microsoft.AspNetCore.Blazor.Browser.JS/src/Services/Http.ts @@ -34,11 +34,11 @@ async function sendAsync(id: number, method: string, requestUri: string, body: s function dispatchSuccessResponse(id: number, response: Response, responseText: string) { const responseDescriptor: ResponseDescriptor = { - StatusCode: response.status, - Headers: [] + statusCode: response.status, + headers: [] }; response.headers.forEach((value, name) => { - responseDescriptor.Headers.push([name, value]); + responseDescriptor.headers.push([name, value]); }); dispatchResponse( @@ -81,6 +81,6 @@ interface ResponseDescriptor { // We don't have BodyText in here because if we did, then in the JSON-response case (which // is the most common case), we'd be double-encoding it, since the entire ResponseDescriptor // also gets JSON encoded. It would work but is twice the amount of string processing. - StatusCode: number; - Headers: string[][]; + statusCode: number; + headers: string[][]; }