This project implements Dart definitions and API helpers for the Bungie.net API. It's based on bungie-api-ts that is meant for use in Destiny Item Manager, but should be general enough to use in any project. The code is completely generated from Bungie's documentation - I considered using something like Swagger Codegen, but instead opted for a custom generator so we could make the result as nice as possible.
add this to your dependencies block in pubspec.yaml
dependencies:
bungie_api: ^12.2.4
There are definitions for every type defined in the Bungie.net services. See their documentation for a list - the interface names are the last part of the full name (for example, Destiny.Definitions.DestinyVendorActionDefinition becomes DestinyVendorActionDefinition). There are a few exceptions, like SingleComponentResponseOfDestinyInventoryComponent, which have been mapped into nicer forms like SingleComponentResponse<DestinyInventoryComponent>, and the server responses, which are now ServerResponse<T> instead of something like DestinyCharacterResponse.
In addition to the types, there are also simple helper functions for each API endpoint. They define the inputs and outputs to that endpoint, and will call a user-provided function with HTTP request info that you can then use to make an HTTP request. This pattern was used so the API helpers could provide full type information. These helpers are not a full API client - they assist in building one. An example:
import 'dart:async';
import 'package:http/http.dart' as http;
import 'package:bungie_api_dart/destiny2.dart';
class BungieApiService{
Future<ServerResponse<DestinyManifest>> getManifest(){
return getDestinyManifest(new Client());
}
}
class Client implements HttpClient{
static const API_KEY = "your_key";
@override
Future<Object> request(HttpClientConfig config) {
if(config.method == 'GET'){
return http.get(config.url, headers: {'X-API-Key': API_KEY});
}
return http.post(config.url, headers: {'X-API-Key': API_KEY});
}
}./install.sh && ./build.sh