[New Features Plans] Some awesome feature are coming for this package user

[Dahkenangnon]

🟢 New features

These features are planned for from now to June 2022.

More description will be push this weekend to explain in more details these features which are coming.
But before all, i want to know your point of view, would you like these features ?

• Going to null safety ( Going to null safety #29 )
• Update documentation
• Testable version of flutter web
• Testable version of flutter desktop
• Add feathers services like api
• Add authentication client
• Update demo app to sound null safety

At the end, this package will be your very cool and very serious choice for flutter mobile app if you like using feathers js rest+realtime api.

[humbugz]

Add offline database support
Add synchronization with remote api

Seem like they'd be ideal!

[Dahkenangnon]

Add offline database support Add synchronization with remote api

Seem like they'd be ideal!

Thank @humbugz for using this package.

These features will be available from now to June 2022 lately.

For any suggestions to improve this package, feel free to create a PR

Cheer 🚀

[Dahkenangnon]

Please let me know if you are interested in these features please.

These feature are in active dev and will pushed, but i want to know if you desire really them.

Thank for you interest.

[dmatuschek]

Add offline database support Add synchronization with remote api

Seem like they'd be ideal!

These would be incredible features 🚀
If it isn't possible yet: Allow developers to initialize the Rest and Socket config separately (especially the baseUrl) or as the official feathers-client, let the developer decide whether to work only with socket or rest. An example:

I host a Feathers API behind a reverse proxy at https://my-app.com/api - then the socket configuration would still need the https://my-app.com/ because the baseUrl of https://my-app.com/api would imply that the socket.io uses "api" as the namespace. On the other hand, the Rest API would still need the https://my-app.com/api as baseUrl. Therefore this should be configurable separately.

An idea for this could be, to initialize the package in flutter like the feathers package. Therefore to keep the mentality of feathers to be independent of the transportation mode and the package is easily extendable for the Primus Client for example.

A example initialization could be:

Socket.io

import 'package:flutter_feathersjs/flutter_feathersjs.dart';
import 'package:socket_io_client/socket_io_client.dart' as IO;

FlutterFeathersjs client = FlutterFeathersjs();
IO.Socket io = IO.io(baseUrl)

client.configure(FlutterFeathersjs.socket(io));

client.service('messages').create({
  text: 'A new message'
});

Rest (With Dio)

import 'package:flutter_feathersjs/flutter_feathersjs.dart';
import 'package:dio/dio.dart';

FlutterFeathersjs client = FlutterFeathersjs();
Dio dio = Dio(BaseOptions(
      baseUrl: baseUrl,
      headers: extraHeaders
));

client.configure(FlutterFeathersjs.rest(dio));

client.service('messages').create({
  text: 'A new message'
});

[Dahkenangnon]

Add offline database support Add synchronization with remote api
Seem like they'd be ideal!

These would be incredible features 🚀 If it isn't possible yet: Allow developers to initialize the Rest and Socket config separately (especially the baseUrl) or as the official feathers-client, let the developer decide whether to work only with socket or rest. An example:

I host a Feathers API behind a reverse proxy at https://my-app.com/api - then the socket configuration would still need the https://my-app.com/ because the baseUrl of https://my-app.com/api would imply that the socket.io uses "api" as the namespace. On the other hand, the Rest API would still need the https://my-app.com/api as baseUrl. Therefore this should be configurable separately.

An idea for this could be, to initialize the package in flutter like the feathers package. Therefore to keep the mentality of feathers to be independent of the transportation mode and the package is easily extendable for the Primus Client for example.

A example initialization could be:

Socket.io

import 'package:flutter_feathersjs/flutter_feathersjs.dart';
import 'package:socket_io_client/socket_io_client.dart' as IO;

FlutterFeathersjs client = FlutterFeathersjs();
IO.Socket io = IO.io(baseUrl)

client.configure(FlutterFeathersjs.socket(io));

client.service('messages').create({
  text: 'A new message'
});

Rest (With Dio)

import 'package:flutter_feathersjs/flutter_feathersjs.dart';
import 'package:dio/dio.dart';

FlutterFeathersjs client = FlutterFeathersjs();
Dio dio = Dio(BaseOptions(
      baseUrl: baseUrl,
      headers: extraHeaders
));

client.configure(FlutterFeathersjs.rest(dio));

client.service('messages').create({
  text: 'A new message'
});

🚀
Greate idea

You should notice i create an issue #28 .

I'll add this possibility before finishing the above planned features and create a new release for it.

Thank @dmatuschek

[Dahkenangnon]

**UPDATE AVAILABLE 🚀 **

Please try the recent pre-release https://pub.dev/packages/flutter_feathersjs/versions/4.1.0-dev

For any discusion about this prelease, please use disccusion under the release. #46