Moya/Moya
Moya
Moya is a network abstraction layer for Swift that provides a structured framework for defining and executing REST API requests. It functions as a type-safe API client that decouples network endpoint definitions from the underlying implementation details to prevent configuration errors and URL typos.
The project distinguishes itself by using protocol-based endpoint definitions and a provider-coordinated execution model. It includes a system for mapping network responses to strongly typed objects and features a dedicated tool for generating type-safe network interface files from external REST documentation.
The framework covers a broad set of capabilities including reactive network programming via wrappers for asynchronous streams, response mapping with HTTP status code filtering, and comprehensive testing utilities for network request stubbing and API mocking.
The library is implemented in Swift.
Features
- RESTful API Clients - Provides a type-safe framework for interacting with RESTful web services using a provider-coordinated model.
- Type-Safe API Clients - Provides a type-safe layer for defining API endpoints to prevent URL typos and enforce parameter correctness via the compiler.
- Response Decoders - Converts raw network response data into usable formats using custom decoding logic for specific data types.
- REST APIs - Provides a structured framework for defining and executing requests to RESTful services.
- Request Execution - Dispatches network requests to defined endpoints and processes results via completion handlers or streams.
- Provider Coordinators - Uses a provider coordinator to manage the entire lifecycle of a network request.
- HTTP Abstraction Layers - Encapsulates low-level network objects to provide a high-level, type-safe API for request and response handling.
- API Response Simulators - Redirects network calls to a local data store to provide predefined stubbed responses for development and testing.
- Network Layer Architectures - Implements a protocol-based abstraction layer that decouples endpoint definitions from network implementation details.
- Protocol-Based API Definitions - Defines network requests as types conforming to a specific protocol to ensure consistent request configurations.
- API Request Mocking - Simulates server responses for testing by intercepting requests and returning pre-defined mock data.
- Type-Safe - Maps strongly typed Swift enums and structs to URL components and request bodies to prevent runtime errors.
- Response Serialization - Maps raw network response data into strongly typed Swift objects using integrated serialization.
- Type-Safe API Frameworks - Transforms raw network bytes into strongly typed JSON objects or images using integrated serialization.
- Type-Safe API Integrations - Ensures type safety across network boundaries by mapping responses to strongly typed Swift objects.
- Testing and Mocking - Includes comprehensive utilities for stubbing network responses and mocking API behavior for testing.
- Validation Filters - Filters network responses by validating that they match specific HTTP status codes before proceeding to decoding.
- HTTP Response Processors - Transforms raw response data into images, JSON, or strings while filtering for successful status codes.
- Reactive Stream Architectures - Wraps asynchronous network calls in observables or publishers to handle responses and progress reactively.
- API Mocking - Simulates server responses with stubbed data to test network integration without live backend requests.
- API Testing - Includes integrated unit testing tools to validate the behavior of API requests and responses.
- Interceptor Chains - Processes network responses through a chain of operators to validate status codes before passing data to decoders.
- Reactive Networking - Provides wrappers for API requests using observables or signal producers to handle responses through reactive streams.
- Networking Frameworks - Provides a network abstraction layer for API services.
- Networking - Network abstraction layer for Swift.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
