Since #140, it becomes convenient to transform HttpRequest or HttpResponse which remapping module has had in charge of. So it'd be better to remove remapping for minimizing confusion by providing same feature in other modules.
Before removal, we should take over features from remapping to gateway module and mark @Deprecate existing. After that, the remapping will be removed in the next version, v0.5.0.
Checklist:
[x] Take over RemappingClient, RemappingRequestStrategy and RemappingResponseStrategy.
Since #140, it becomes convenient to transform
HttpRequestorHttpResponsewhichremappingmodule has had in charge of. So it'd be better to removeremappingfor minimizing confusion by providing same feature in other modules. Before removal, we should take over features fromremappingtogatewaymodule and mark@Deprecateexisting. After that, theremappingwill be removed in the next version, v0.5.0.Checklist:
RemappingClient,RemappingRequestStrategyandRemappingResponseStrategy.140
RemappingRequestPathStrategy141
RemappingResponseStatusStrategy146
remappingmodule