Added exported imports for several Alamofire types. #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While TRON is a wrapper around
Alamofire
API's, several ofAlamofire
types have been exposed through TRON interface, forcing a user to explicitly writeimport Alamofire
along withimport TRON
to use them.It's possible to write an implicit import, that exports entire framework to another framework users(see example, advanced example). TRON - Alamofire situation is a little different, however, since TRON wraps some API's and discourages user from using Alamofire API's directly.
Therefore, this PR aims to export only specific types from Alamofire, that are actually exposed by TRON API.
Downside of this PR is that if TRON API user had local API's that clash with Alamofire naming(for example, local
Session
type, or localRequest
type), this change would actually be breaking and would require to explicitly disambiguate those types(Alamofire.Request
).