relay

Summary Fixes a batch of duplicated-word typos in code comments and documentation. These are all self-evident repeated-word mistakes (e.g. "the the", "to to", "is is", "are are", "a a") that hurt readability. No behavior changes — comments, docblocks, and Markdown/MDX docs only. Changes Notes Only the canonical sources were edited; frozen snapshots were intentionally left untouched. Verified that grammatically-correct sequences (e.g. "indicates ... that that ID is stable") were not changed.

First off — thank you! We've been building on Relay for nearly three years and it's been fantastic. We're especially happy that the TypeScript types are now maintained directly in this repo: it's what makes contributions like this one straightforward, and we're glad to be able to give a little back to the core team and the community. 🙏 / are written in Flow but ship hand-written files for TypeScript consumers. Since nothing generates them from the Flow source, they can drift. This PR fixes three such drifts (declarations only — no Flow/runtime changes). The motivating one for us was #3: a real type bug, not just a gap. Mutations using at the root level are correctly typed in Flow but were falsely rejected by the TypeScript types, which we've had to work around by overriding Relay's types in our own codebase. Fixing it at the source removes that workaround for everyone. The two missing declarations (#1) we hit along the way. 1. Add two hooks that had no TypeScript types and are exported from but had no , making them invisible to TypeScript. Added declarations for both and re-exported them from . Both are constrained on (matching the Flow sources, which don't constrain the response, and consistent with the other modern hooks). 2. Add the missing prop to The Flow component accepts this optional prop but the omitted it, so passing it was a type error. 3. Fix so mutations type-check The Flow type uses ("any object") for //, but the translated it as , which requires an index signature. Responses that lack one — notably the unions from mutations, and interface-typed responses — are valid in Flow but were rejected by TypeScript, forcing consumers to override Relay's types locally. Fixed by translating faithfully as : This only widens a constraint, so it's backward compatible — nothing that compiled before breaks. Fixing it at the source corrects the whole mutation surface at once (, , , , …), so itself needs no special-casing. Testing Verified via linking the files directly in our monorepo and removing our local shims / ts overwrites that we currently have to have.

Summary The function hardcoded as the only allowed path separator, but on Windows operations produce separators This caused to be flagged as a disallowed character, making all sharded extra-artifact paths fall back to the flat layout on Windows Replace the literal with which handles both (all platforms) and (Windows) Fixes the CI failures: Test plan [x] All 6 tests pass locally on macOS [ ] Windows CI should now pass (the two previously failing tests should produce correct sharded paths instead of falling back to flat layout)