> For the complete documentation index, see [llms.txt](https://cbwire.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cbwire.ortusbooks.com/releases/whats-new-with-3.0.md).

# What's New With 3.0

05/18/2023

## New Features

### Single File Components

Combine component logic and template in a single file using `@startWire` and `@endWire` markers.

```html
<!-- wires/Counter.cfm -->
<cfscript>
    // @startWire
    data = {
        "counter" = 0
    };
    
    function increment() {
        data.counter += 1;
    }
    // @endWire
</cfscript>

<cfoutput>
<div>
    <h2>Counter: #counter#</h2>
    <button wire:click="increment">+</button>
</div>
</cfoutput>
```

### Module-Aware Components

Components can now be organized within ColdBox modules.

```html
<!-- Load component from specific module -->
#wire("ProductCard@shop", { "productId": 123 })#
#wire("cards.ProductCard@shop", { "productId": 123 })#
```

## Enhancements

### Removed cbValidation Dependency

CBWIRE no longer requires cbValidation, making it more lightweight.

### Simplified Property Access

Templates now use direct property access instead of the `args` scope:

```html
<!-- Old (2.x) -->
<cfoutput>#args.name# - #args.computed.getFullName()#</cfoutput>

<!-- New (3.0) -->
<cfoutput>#name# - #getFullName()#</cfoutput>
```

### Performance Improvements

* Skip unnecessary ColdBox view caching/lookups
* Streamlined engine architecture
* Removed `computedPropertiesProxy` for better performance

## Bug Fixes

* Fixed empty string/null values not passing to Livewire
* Support full-path wire resolution (e.g., `appMapping.wires.SomeComponent`)
* Ensure data-updating actions trigger DOM updates
* `.see()` / `.dontSee()` in tests now chain correctly
* Fix computed property overrides in component tests

## Breaking Changes

### Property Access

```html
<!-- Before -->
<cfoutput>#args.name#</cfoutput>
<!-- After -->
<cfoutput>#name#</cfoutput>
```

### Computed Properties

```html
<!-- Before -->
<cfoutput>#args.computed.getDisplayName()#</cfoutput>
<!-- After -->
<cfoutput>#getDisplayName()#</cfoutput>
```

### Validation Constraints

```javascript
// Before
this.constraints = { "email" = { "required" = true } };
// After
constraints = { "email" = { "required" = true } };
```

### Event Emission

```javascript
// Before
emitTo("event-name", "ComponentName");
// After
emitTo("ComponentName", "event-name");
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cbwire.ortusbooks.com/releases/whats-new-with-3.0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.