mirror of
https://github.com/Moya/Moya.git
synced 2026-03-18 19:52:28 +00:00
31 lines
1.4 KiB
Markdown
31 lines
1.4 KiB
Markdown
# Documentation
|
|
|
|
Moya is about working at *high levels of abstraction* in your application.
|
|
It accomplishes this with the following pipeline.
|
|
|
|
|
|
|
|
----------------
|
|
|
|
<p align="center">
|
|
<a href="Targets.md">Targets</a> • <a href="Endpoints.md">Endpoints</a> • <a href="Providers.md">Providers</a> • <a href="Authentication.md">Authentication</a> • <a href="ReactiveSwift.md">ReactiveSwift</a> • <a href="RxSwift.md">RxSwift</a> • <a href="Threading.md">Threading</a> • <a href="Plugins.md">Plugins</a> • <a href="Testing.md">Testing</a>
|
|
</p>
|
|
|
|
----------------
|
|
|
|
You _should not_ have to reference Alamofire directly. It's an _awesome_
|
|
library, but the point of Moya is that you don't have to deal with details
|
|
that are that low-level.
|
|
|
|
(If you _need_ to use Alamofire, you can pass in a `SessionManager` instance to the
|
|
`MoyaProvider` initializer.)
|
|
|
|
If there is something you want to change about the behaviour of Moya, there is
|
|
probably a way to do it without modifying the library. Moya is designed to be
|
|
super-flexible and accommodate the needs of every developer. It's less of a
|
|
framework _of code_ and more of a framework of _how to think_ about network
|
|
requests.
|
|
|
|
Remember, if at any point you have a question, just [open an issue](http://github.com/Moya/Moya/issues/new)
|
|
and we'll get you some help.
|