<commit_before># Change Log

All notable changes to this project will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org/).

## 0.7.0

### Added

* By default, the `fetch` higher order component will fetch data when mounted or updated, unless specified to do otherwise using `shouldFetchOnMount()` or `shouldFetchOnUpdate()` options.

### Removed

* The `forceInitialFetch` option was removed in favor of the `shouldFetchOnMount()` function, which can be configured globally with `fetch.setup()`.

## 0.6.0

### Added

* Forward props passed to wrapped components to `getInitialAsyncState`. It allows developers to access props passed from React Router to their components. Unfortunately, in universal applications, populating this parameter requires the developer to pass it to `fetchRouteData`, potentially leading to discrepancies since React Router provide slightly different properties.

## 0.5.0<commit_msg>Update CHANGELOG file<commit_after># Change Log

All notable changes to this project will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org/).

## 0.8.0

## Change

* Rename options that indicate whether HOC should fetch on mount or update
* Fix issue where `setState()` is called after components are unmounted
* Fix issue where fetchers are called multiple times between route transitions
* Fix issue where application state is not injected into `shouldFetchOnUpdate` option
* Fix issue where rendering errors are swallowed in promise chain

## 0.7.0

### Added

* By default, the `fetch` higher order component will fetch data when mounted or updated, unless specified to do otherwise using `shouldFetchOnMount()` or `shouldFetchOnUpdate()` options.

### Removed

* The `forceInitialFetch` option was removed in favor of the `shouldFetchOnMount()` function, which can be configured globally with `fetch.setup()`.

## 0.6.0

### Added

* Forward props passed to wrapped components to `getInitialAsyncState`. It allows developers to access props passed from React Router to their components. Unfortunately, in universal applications, populating this parameter requires the developer to pass it to `fetchRouteData`, potentially leading to discrepancies since React Router provide slightly different properties.

## 0.5.0
{'fraction_non_alphanumeric': 0.07210708117443869, 'fraction_numerical': 0.009067357512953367, 'mean_word_length': 5.1786666666666665, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1716468', 'n_tokens_mistral': 576, 'n_tokens_neox': 546, 'n_words': 289}