Saiichi Shayan Hashimoto

```typescript const query = "false[true]"; const tree = parse(query); const result = await (await evaluate(tree)).get(); console.log(result); // Should be false, is null ``` According to the GROQ spec's [section on...

Unreleased packages should still trigger dependent releases

1

If the dependency of packages is A depends on B depends on C, then a change in C triggers a release in A & B, which is good. The issue...

useLocalStorage mismatches server render

15

Any server rendering solution won't have access to a browser's local storage, so it will default to the `initialValue`. Since `useLocalStorage` will use the actual local storage value on first...

Rename `resolve[d]` to `resolve[d]Mock`

4

As @mckelveygreg made clear in #158, some things about "resolve" are unclear: - `s.resolved` should be the type but with references resolved. Right now it's both parsed AND resolved. These...

`s.crossDatasetReference` https://www.sanity.io/docs/cross-dataset-reference-type I've never used it (it's an enterprise feature) but it's there.

https://www.sanity.io/docs/array-type#c1a07c0b34ec Maybe we can do this like `s.number` and `s.string` where it narrows the inferred types.

Test typescript performance

1

It would be really nice to test the performance of type checking, similar to [jest's `testTimeout`](https://jestjs.io/docs/configuration#testtimeout-number) (which I'm fairly confident only sets a timeout for the _runtime_ of the test,...

An idea that @judofyr suggested was essentially a polyfill. Rather than switching imports to `@sanity-typed`, we could enable importing something like `@sanity-typed/polyfill` and it would globally augment `sanity`'s native packages...