-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merged PR 3858: FEAT: The SetHeadersElement can be used to convert va…
…lues from all 'SetHeader*' properties into a dictionary that can be used to populate the HTTP response headers - FEAT: The SetHeadersElement can be used to convert values from all 'SetHeader*' properties into a dictionary that can be used to populate the HTTP response headers. This element is added automatically for web integration pipelines. - FEAT: When using web integration, the pipeline will now automatically set HTTP headers in the response based on the values of properties starting with 'SetHeader' - For ASP.NET core, setting the response headers is handled by the SetHeadersService - For ASP.NET , setting the response headers is handled by the SetHeadersProvider - REFACTOR: Combine the separate 'options' configuration classes for ASP.NET Core and ASP.NET into a single class. Add an option to flag the 'SetHeader' functionality on/off. - BUG: Should only try and read from the 'Form' property on an HTTP request after checking if the content type is correct. This addresses #5 . - BUG: ASP.NET Framework integration was not reading form parameters. This has now been corrected. - TEST: Add some tests to verify that the functionality to add form parameters to evidence in the WebRequestEvidenceService is functioning correctly. - TEST: Add a new JsonBuilderElement test to verify the javascriptProperties element in the JSON for properties with type JavaScript, AspectPropertyValue<JavaScript> or IAspectPropertyValue<JavaScript>. - TEST: Modify the JsonBuilderElement tests to verify that the delayed evidence functionality works correctly is the property type is JavaScript, AspectPropertyValue<JavaScript> or IAspectPropertyValue<JavaScript>. - BUG: Correct a bug that stopped properties from being included in the javascriptProperties list if they had type AspectPropertyValue<JavaScript>. - BUG: JsonBuilderElement was not correctly checking JavaScript types when getting delayed execution properties. This has now been corrected. Also moved the type check to a static utility class. - DOC: Commented the UseFiftyOne extension method to make it clear that it must be called before any ExceptionHandlerExtensions methods. - BUILD: Use common-ci template. Related work items: #4382, #4383
- Loading branch information
Showing
62 changed files
with
2,629 additions
and
588 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,6 @@ | ||
[submodule "FiftyOne.Pipeline.Elements/FiftyOne.Pipeline.JavaScriptBuilderElement/Templates/javascript"] | ||
path = FiftyOne.Pipeline.Elements/FiftyOne.Pipeline.JavaScriptBuilderElement/Templates/javascript | ||
url=../javascript | ||
url=../javascript | ||
[submodule "ci/common-ci"] | ||
path = ci/common-ci | ||
url=../common-ci |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.