Skip to content
This repository was archived by the owner on Apr 13, 2023. It is now read-only.

Changelog.md

Latest commit

 

History

History
228 lines (133 loc) · 7.84 KB

Changelog.md

File metadata and controls

228 lines (133 loc) · 7.84 KB

Change log

Expect active development and potentially significant breaking changes in the 0.x track. We'll try to be diligent about releasing a 1.0 version in a timely fashion (ideally within 1 or 2 months), so that we can take advantage of SemVer to signify breaking changes from that point on.

vNext

  • Feature: Remove nested imports for apollo-client. Making local development eaiser. #234
  • Feature: Move types to dev deps #251
  • Feature: New method for skipping queries which bypasses HOC internals #253
  • Feature: Integrated subscriptions! #256
  • Feature: Refactor loading state managment to use apollo-client fully. Reduces library size by ~50% #211

v0.5.7

  • Feature: Upgraded to typescript 2.0 #217
  • Feature: Allow usage of redux key or selector #226

v0.5.6

  • Bug: Passing immutable to ApolloProvider breaks ssr. renderToStringWithData fails to reference the right store. #222
  • Bug: Fixed issue with context in SSR #218

v0.5.5

  • Bug: Fixed lifecycle events for componentWillMount() on the server #205

v0.5.4

  • Bug: Created better reference to updateQuery when bound early. It will also throw if called before it should be.

v0.5.3

  • Bug: Fixed issue with updateQuery not being present during componentWillMount #203

v0.5.2

  • Feature: Allow optional variables by passing null value on behalf of the variable #200

v0.5.1

  • Feature: Added link to recompose to use the compose function. This makes it easy to combine multiple queries on a single component. #194

v0.5.0

Breaking

// old
renderToStringWithData(component).then(markup) // markup had a script tag

// new

renderToStringWithData(component).then({ markup, initialState }) // markup has not tag, and state is passed

  • Feature: Removed client as a prop and fixed warnings when not using ApolloProvider #189

  • Feature: Added updateQuery to data props

  • Bug: Fixed renderToStringWithData causing react warning #169

  • Bug: Fixed ssr fragment issue #178

  • Bug: Fixed loading state for skipped queries #190

  • Bug: Fixed loading state on remounted component with different variables

v0.4.7

  • Bug: Fixed SSR issue with context #165
  • Bug: Fixed issue when context changes in parent container not going through to child; #162
  • Bug: Fixed loading state on remount of forceFetch operations; #161

v0.4.6

  • Bug: Fixed issue with variable merging after fetchMore #150

v0.4.5

  • Feature: Allow options value to be an object instead of a method. #144
  • Bug: Fixed issue with missing methods on initial props #142
  • Bug: Fixed oddity with multi nested enhancers on SSR #141

v0.4.4

  • Bug: Fixed issue with variable merging #139

v0.4.3

  • Feature: Support a different store in the tree that is immutable (support immutable redux) #137

v0.4.2

  • Bug: Fixed refetch methods when no result is returned

v0.4.1

v0.3.20

  • Bug: Fixed loading state on refetch more when data doesn't change
  • Feature: added fetchMore #123

v0.3.19

  • Bug: Retain compatibility with version 0.3.0 of Apollo Client via a backcompat shim. #109

v0.3.18

  • Feature: Support 0.4.0 of Apollo Client, and pass through new mutation options #105 #106

v0.3.17

  • Bug: Fixed but where SSR wouldn't get calculated props from redux actions #103

v0.3.16

  • Feature: integrated SSR #83
  • Feature: added ability to hoist statics on components #99
  • Bug: Don't strip data away from the component when the query errors #98

v0.3.15

  • Bug: Fixed issue where react native would error on aggressive cloneing of client

v0.3.14

  • Feature: pass through all methods on apollo client

v0.3.13

  • Bug: fixed issue causing errors to be passed to apollo-client #89

v0.3.11/12

  • Bug: fixed overrendering of components on redux state changes

v0.3.10

  • Bug: fixed bug where SSR would fail due to later updates. This should also prevent unmounted components from throwing errors.

v0.3.9

  • Feature: provide add watchQuery to components via connect

v.0.3.8

  • Bug: Don't use old props on store change change

v.0.3.7

  • Bug: Reset loading state when a refetched query has returned

v0.3.6

  • Bug: Loading state is no longer true on uncalled mutations.
  • Improvement: don't set the loading state to false if forceFetch is true

v0.3.5

Return promise from the refetch method

v0.3.4

  • Bug: Fix bug where state / props weren't accurate when executing mutations.
    • Improvement: Increase performance by limiting re-renders and re-execution of queries. Chore: Split tests to make them easier to maintain.

v0.3.2 || v0.3.3 (publish fix)

  • Feature: add startPolling and stopPolling to the prop object for queries
  • Bug: Fix bug where full options were not being passed to watchQuery

v0.3.1

  • Feature: Support 0.3.0 of apollo-client

v0.3.0

  • Feature: Change Provider export to be ApolloProvider and use Provider from react-redux

v0.2.1

  • Feature: Support 0.1.0 and 0.2.0 of apollo-client

v0.2.0

Breaking change:

  • Feature: Remove result key in favor of dynamic key matching root fields of the query or mutation. (#31)
{
  loading: false,
  result: {
    posts: []
  }
}

becomes

{
  loading: false,
  posts: []
}

v0.1.5

  • Bug: Get state directly from redux store internally

v0.1.4

  • Bug: Fix bug with willReceiveProps

v0.1.2

Bug: - Adjust loading lifecycle marker to better match the behavior of apollo-client #11

v0.1.1

Feature: - Update to support new observable API from apollo-client #9

v0.1.0

Initial release. Brings in support for binding GraphQL data to components easily as well as perform mutations.

We didn't track changes before this version.