# What's New With 2.2

## 01/09/2022

### Enhancements

[CBWIRE-99](https://ortussolutions.atlassian.net/browse/CBWIRE-99): Implement lifecycle hook onHydrate().

[CBWIRE-100](https://ortussolutions.atlassian.net/browse/CBWIRE-100): Implement lifecycle hook onHydrate\[Property]\().

[CBWIRE-103](https://ortussolutions.atlassian.net/browse/CBWIRE-103): Implement an automatic trim() for all data properties.

[CBWIRE-124](https://ortussolutions.atlassian.net/browse/CBWIRE-124): Implement the ability to interact with CBWIRE component from JavaScript using cbwire.find( '#args.\_id#' ).

[CBWIRE-125](https://ortussolutions.atlassian.net/browse/CBWIRE-125): Add configuration setting 'enableTurbo' to automatically include everything needed to work with Turbo for single page applications.

[CBWIRE-130](https://ortussolutions.atlassian.net/browse/CBWIRE-130): Add ability to call reset() without passing a key to reset all data properties to their original values.

### Changed

[CBWIRE-93](https://ortussolutions.atlassian.net/browse/CBWIRE-93): Implement onMount() method instead of mount().

### Bug Fixes

[CBWIRE-121](https://ortussolutions.atlassian.net/browse/CBWIRE-121): DocBox generated docs are failing because of file structure.

[CBWIRE-126](https://ortussolutions.atlassian.net/browse/CBWIRE-126): Listeners are being fired immediately when calling emit() when the listener is defined on the same component, which they shouldn't.

[CBWIRE-127](https://ortussolutions.atlassian.net/browse/CBWIRE-127): onHydrate() is firing after actions are performed.

[CBWIRE-129](https://ortussolutions.atlassian.net/browse/CBWIRE-129): Computed properties are not being rendered before actions are called.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cbwire.ortusbooks.com/3.x/release-history/whats-new-with-2.2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.