Bug Fix
query().query() no longer throws on second call (#35)
Calling .query() on a resource field worked fine the first time, but threw a TypeError on any subsequent call:
TypeError: Cannot assign to read only property '0' of object '[object Array]'
Root cause: When comwit caches query results internally, it deep-freezes the snapshot via Object.freeze. On the next .query() call, the cached (frozen) state was restored into the reactive proxy — but the proxy's wrap() function tried to mutate the frozen array in-place to set up reactivity, causing the TypeError.
Fix: The proxy engine now shallow-clones any frozen object before wrapping it, so frozen snapshots from the cache are never mutated directly. (PR #36)
This affected any query() field where data was an array or nested object — which is virtually every real-world use case.
Upgrade
yarn add comwit@0.2.1
Drop-in replacement. No API changes.