Fix interceptor JSON casing

[martincostello]

Fix property casing of Swagger UI interceptor function properties.

Resolves #2906.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.89%. Comparing base (ecce973) to head (969cc9d).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2907   +/-   ##
=======================================
  Coverage   89.89%   89.89%           
=======================================
  Files          72       72           
  Lines        2711     2711           
  Branches      429      429           
=======================================
  Hits         2437     2437           
  Misses        274      274           

Flag	Coverage Δ
Linux	89.89% <100.00%> (ø)
Windows	89.89% <100.00%> (ø)
macOS	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[domaindrivendev]

Given that the rest of the config properties are serialized to camel case, I wonder would it be better to maintain that consistency and just update the assignment in index.html?

Swashbuckle.AspNetCore/src/Swashbuckle.AspNetCore.SwaggerUI/index.html

Lines 99 to 103 in 432c417

	var interceptors = JSON.parse('%(Interceptors)');
	if (interceptors.RequestInterceptorFunction)
	configObject.requestInterceptor = parseFunction(interceptors.RequestInterceptorFunction);
	if (interceptors.ResponseInterceptorFunction)
	configObject.responseInterceptor = parseFunction(interceptors.ResponseInterceptorFunction);

[domaindrivendev]

Just a thought but not a showstopper for me other than that looks good 👍

[domaindrivendev]

doh didn't realize we had auto-merge - oh well I guess we leave it as is

[martincostello]

I did consider renaming it, but this persuaded me to leave it alone: #2906 (comment)