You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
The decision here is to add a new filter stage that will surround:
Exception Filter > Model Binding > Action Filter > Action
Result Filter > Result
Working name is Resource Filter.
Primary scenario here is to support modifications to the inputs to model binding. Anything else where you need to surround the whole action and result is a good candidate to also use this stage.
See diagram:
How to expose input formatters:
Option 1. As an auth filter
Option 2. As a new filter stage which runs after auth and before deserialization.
Option 3. Implement as an action filter and let the deserialization be lazy.
The text was updated successfully, but these errors were encountered:
The call is to expose a new filter stage which runs after auth and before deserialization. Changing the title to reflect the same.
harshgMSFT
changed the title
Input content negotiation- surfacing input formatters.
Add a new filter stage for modifying input formatter collection.
Aug 19, 2014
The decision here is to add a new filter stage that will surround:
Working name is Resource Filter.
Primary scenario here is to support modifications to the inputs to model binding. Anything else where you need to surround the whole action and result is a good candidate to also use this stage.
See diagram:
How to expose input formatters:Option 1. As an auth filter
Option 2. As a new filter stage which runs after auth and before deserialization.
Option 3. Implement as an action filter and let the deserialization be lazy.
The text was updated successfully, but these errors were encountered: