v2.1.1-beta.1@beta

2.1.1-beta.1 (2019-08-30)

Bug Fixes

• client: default toEncodable (5f938e4)
• client: patch fetchMore to write to cache (9cb7474)
• client: use noCache for fetchMore, avoiding normalization (da20541)
• add eager result to stream, rebuild query widget on var change (af89b19)

v2.1.0

2.1.0 (2019-08-12)

Bug Fixes

• add fetchmore param (80ed216)
• assert to ensure updateQuery doesn't return null (625c838)
• pass fetch more variable and set combined data (8b8e4c7)
• remove unnecessary fields in fetchmoreoptions (17b429c)
• removed updateVariables (d4b0b3f)

Features

• client: add fetchmore query options (7208e00)
• graphql-flutter: add method for pagination (47b96e8)
• graphql-flutter: name variables more appropriately (4435b4d)
• more error handling in fetchMore, updateVariables (but will remove) (8be71b8)
• move fetch more method to observable query (36d6229)
• set loading variable to true, when fetching more (24d656a)
• update minimum sdk requirements (63a5c30)

v2.1.0-beta.1@beta

2.1.0-beta.1 (2019-08-05)

Bug Fixes

• add fetchmore param (80ed216)
• assert to ensure updateQuery doesn't return null (625c838)
• pass fetch more variable and set combined data (8b8e4c7)
• remove unnecessary fields in fetchmoreoptions (17b429c)
• removed updateVariables (d4b0b3f)

Features

• client: add fetchmore query options (7208e00)
• graphql-flutter: add method for pagination (47b96e8)
• graphql-flutter: name variables more appropriately (4435b4d)
• more error handling in fetchMore, updateVariables (but will remove) (8be71b8)
• move fetch more method to observable query (36d6229)
• set loading variable to true, when fetching more (24d656a)
• update minimum sdk requirements (63a5c30)

v2.0.1

2.0.1 (2019-08-04)

Bug Fixes

• client: error handling (5c0f2e5)

v2.0.0

2.0.0 (2019-07-13)

Bug Fixes

• cache: don't use super.read in denormalizedRead so OptimisticCache overrides it's behavior (38d3588)
• remove and gitignore pubspec.lock files (6e31f02)
• ci: simply re-export multipartFileFrom utility (855dc6d)
• client: crashed upload file (da49567), closes #336
• client: do not mutate input data (d30460e), closes #295
• flutter: compatible with path_provider usage (ee0cb58)
• graphql: add flutter auto-gen files to gitignore (f29188c)
• graphql: delete flutter autogen files (44ee7f9)
• graphql: ignore directory not directory content (ba77a1b)

Features

• cache: handle full blown cyclical pointers in normalization (c4fba99)
• client: cache is supported in web/browser platform (9ada687)
• client: Introduce QueryResultSource for more informative result (e3353e5)
• client: support GraphQL upload files on browser (70c7f74)
• client: websocket usable on browser (08305db)
• client: websocket usable on browser (47aafee)
• flutter: eagerly fetch query results (13fd8f7)

BREAKING CHANGES

• client: InMemoryCache no longer accept storageProvider,
  however this param has always been using for testing only.

The naming InMemoryCache is also debatable, as both io and html
implementation of this class is based on "persistent storage", not at all
"in memory".

There are refactor works to do to consolidate in_memory_* files.

v1.1.1-beta.8@beta

1.1.1-beta.8 (2019-06-28)

Bug Fixes

• client: crashed upload file (da49567), closes #336

v1.1.1-beta.7@beta

1.1.1-beta.7 (2019-06-10)

Features

• client: Introduce QueryResultSource for more informative result (e3353e5)
• flutter: eagerly fetch query results (13fd8f7)

v1.1.1-beta.6

1.1.1-beta.6 (2019-06-07)

Bug Fixes

• ci: simply re-export multipartFileFrom utility (855dc6d)

v1.1.1-beta.5

1.1.1-beta.5 (2019-06-06)

Features

• client: websocket usable on browser (08305db)
• client: websocket usable on browser (47aafee)

v1.1.1-beta.4

1.1.1-beta.4 (2019-06-05)

Bug Fixes

• flutter: compatible with path_provider usage (ee0cb58)

Features

• client: cache is supported in web/browser platform (9ada687)
• client: support GraphQL upload files on browser (70c7f74)

BREAKING CHANGES

• client: InMemoryCache no longer accept storageProvider,
  however this param has always been using for testing only.

The naming InMemoryCache is also debatable, as both io and html
implementation of this class is based on "persistent storage", not at all
"in memory".

There are refactor works to do to consolidate in_memory_* files.