fnx_rest 2.0.1

  • README.md
  • CHANGELOG.md
  • Installing
  • Versions
  • 58

fnx_rest #

Set of REST tools which work nicely with Dart 2 / Angular.

This is a plain old REST client, if you are looking for something more sophisticated, try streamy for instance.

fnx_rest is oriented to be developer and Angular friendly and is particularly useful when creating boring CRUD applications with many similar API calls.

Example #

import 'package:fnx_rest/fnx_rest_browser.dart';
# import 'package:fnx_rest/fnx_rest_io.dart'; (when not in a browser)       

RestClient root = BrowserRestClient.root("/api/v1");        
RestResult response = await root.child("/users").get();
List users = response.data;

Angular support #

You can define root REST client, add your API keys and other additional headers to it and inject this root client with Angular's dependency injection to your elements and/or services.

RestClient root = BrowserRestClient.root("/api/v1");            
      
# your component
class MyApp {
    RestClient restRoot;
    MyApp(this.restRoot);        
}

# add custom headers, for example after user's signing in
restRoot.setHeader("Authorization", authKey);       

(see Angular docs for DI details)

RestClient is hierarchical:

RestClient root = BrowseRestClient.root("/api/v1");   //  /api/v1
RestClient users = root.child("/users");            //  /api/v1/users            
RestClient john = users.child("/123");              //  /api/v1/users/123

All children inherit configuration of their parents, but are allowed to override it.

RestClient supports query parameters:

RestClient limitedUsers = users.setParam('limit', '1000');  //  /api/v1/users?limit=1000            

All children inherit configuration of their parents, but are allowed to override it.

Typically you would create a child of the root rest client in your component like this:

class UserManagement {
    RestClient users;
    UserManagement(RestClient root) {
        users = root.child("/users"); // endpoint /api/v1/users
    }
}

Every instance of RestClient has bool working property, which indicates whether this client is currently processing a request/response or not. You can use it to indicate "working" state to the user:

<p *ngIf="users.working">Sending user data to server ...</p>

This property is recursively propagated to client's parents so you can indicate this "working" state on any level. Locally (for a form), or globally (for the whole app).

// update user     
users.put(...);

Until the request is processed, john.working == true, users.working == true and root.working == true.

// read users
users.get( ... )

In this case john.working == false but users.working == true and root.working == true.

You can easily use this behaviour to disable a form and all it's buttons after submitting edited user data, but in the same time you can have universal global indicator of any HTTP communication (in your app status bar, for example).

HTTP methods #

RestClient has following methods:

Future<RestResult> get({dynamic data, Map<String, String> headers}) ...
Future<RestResult> post(dynamic data, {Map<String, String> headers}) ...
Future<RestResult> put(dynamic data, {Map<String, String> headers}) ...
Future<RestResult> delete({dynamic data, Map<String, String> headers}) ...
Future<RestResult> head({Map<String, String> headers}) ...

Use optional parameter headers to specify custom ad-hoc headers you need in this call only. Headers will be merged with your RestClient default headers, it's parent's headers etc. up to the root RestClient.

Don't use this parameter to specify Content-Type or Accept headers, see below.

RestResult #

Each call returns Future<RestResult>. RestResult contains status (HTTP status, int) and data which are already converted to your desired type (see below) - Dart Map or Dart List by default.

Request/response serialization #

By default, the root client is configured to produce and consume JSON and Dart Maps and Lists. You can easily customize this behaviour to accept or produce any binary data:

RestClient img = root.child("/images");        //  /api/v1/images     
img.acceptsBinary("image/png");
img.producesBinary("image/png");

Such data will be sent and received as List<int> or inject any custom text based serialization or deserialization you need:

/*
typedef dynamic Serializer(dynamic payload);
typedef dynamic Deserializer(String payload);
*/

client.accepts("text/csv", myCsvDeserializeFunction);
client.produces("text/csv", myCsvSerializeFunction);

This configuration is inherited by client's children.

Work in progress #

Suggestions, pull requests and bugreports are more than welcome.

Changelog #

0.0.1 #

  • Initial version

Use this package as a library

1. Depend on it

Add this to your package's pubspec.yaml file:


dependencies:
  fnx_rest: ^2.0.1

2. Install it

You can install packages from the command line:

with pub:


$ pub get

with Flutter:


$ flutter packages get

Alternatively, your editor might support pub get or flutter packages get. Check the docs for your editor to learn more.

3. Import it

Now in your Dart code, you can use:


import 'package:fnx_rest/fnx_rest.dart';
  
Version Uploaded Documentation Archive
2.0.1 Sep 12, 2018 Go to the documentation of fnx_rest 2.0.1 Download fnx_rest 2.0.1 archive
2.0.0 Aug 2, 2018 Go to the documentation of fnx_rest 2.0.0 Download fnx_rest 2.0.0 archive
0.5.0 Dec 7, 2016 Go to the documentation of fnx_rest 0.5.0 Download fnx_rest 0.5.0 archive
Popularity:
Describes how popular the package is relative to other packages. [more]
28
Health:
Code health derived from static analysis. [more]
99
Maintenance:
Reflects how tidy and up-to-date the package is. [more]
70
Overall:
Weighted score of the above. [more]
58
Learn more about scoring.

We analyzed this package on Feb 20, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:

  • Dart: 2.1.0
  • pana: 0.12.13+1

Platforms

Detected platforms: Flutter, other

Primary library: package:fnx_rest/fnx_rest.dart with components: io.

Health suggestions

Fix lib/src/rest_listing.dart. (-1 points)

Analysis of lib/src/rest_listing.dart reported 2 hints:

line 32 col 43: Use = to separate a named parameter from its default value.

line 67 col 7: Use rethrow to rethrow a caught exception.

Fix lib/src/rest_client.dart. (-0.50 points)

Analysis of lib/src/rest_client.dart reported 1 hint:

line 141 col 15: Don't explicitly initialize variables to null.

Format lib/fnx_rest.dart.

Run dartfmt to format lib/fnx_rest.dart.

Format lib/fnx_rest_browser.dart.

Run dartfmt to format lib/fnx_rest_browser.dart.

Format lib/fnx_rest_io.dart.

Run dartfmt to format lib/fnx_rest_io.dart.

Maintenance suggestions

The package description is too short. (-20 points)

Add more detail to the description field of pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.

Maintain an example. (-10 points)

Create a short demo in the example/ directory to show how to use this package.

Common filename patterns include main.dart, example.dart, and fnx_rest.dart. Packages with multiple examples should provide example/README.md.

For more information see the pub package layout conventions.

Dependencies

Package Constraint Resolved Available
Direct dependencies
Dart SDK >=2.0.0-dev.61.0 <3.0.0
http ^0.11.3+17 0.11.3+17 0.12.0+1
logging ^0.11.3 0.11.3+2
Transitive dependencies
async 2.0.8
charcode 1.1.2
collection 1.14.11
http_parser 3.1.3
meta 1.1.7
path 1.6.2
source_span 1.5.4
string_scanner 1.0.4
term_glyph 1.1.0
typed_data 1.1.6
Dev dependencies
mockito ^3.0.0
test ^1.3.0