Move link logic to separate package

aerogear / offix

GraphQL Offline Client and Server

https://offix.dev

Apache License 2.0

760 stars 45 forks source link

Move link logic to separate package #4

Closed wtrocki closed 5 years ago

wtrocki commented 5 years ago

Feature Request

Split conflict and offline features with client creation so developers can pick them separately and integrate with their apps.

wtrocki commented 5 years ago

@StephenCoady @darahayes I think we might instead have conflict and offline as single package with thin client wrapping both helpers and links.

This way we can:

promote links in apollo
have very opiniated client that works out of the box
have cache helpers as separate tooling for ecosystem
use links to provide different flavours of offix ;)

Sounds like plan?

StephenCoady commented 5 years ago

It sounds good to me. A completely pluggable package with a client that ties everything together if required is the best of both.

darahayes commented 5 years ago

I really like this idea. I would go as far as to say we could split out all of the links into dedicated packages. (Offline, Conflicts, Auth, etc) Then we can provide a composite link or even an entire client that uses those in an opinionated way.

wtrocki commented 5 years ago

Perfect! Added that to an upstream roadmap, to be taken after conflict package is done