captbaritone / captbaritone/grats

Running Grats on Deno

Open
#16 4 comments 2 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
358
Forks
24
PR merge metrics
No merged PRs in 30d

Description

Here's a repo that runs [repo](https://github.com/mandx/denograts) and documents some warts and workarounds.

What I have found so far:
* Scalars provided by Grats (`import { Float, Int, ID } from "grats"`) are importable just fine, but seems like the docblocks aren't reachable.
* Kinda makes sense: these imports are importmaps managed by Deno; I'm guessing Grat's Typescript compiler can't locate the actual file where the scalars are defined, the file containing the scalars' dockblocks.
* A not-so-terrible workaround is to "vendor" the scalar definitions, so they are fully accessible by Grat's (see `schema.ts` in this repo).
* Module remapping must be done carefully to ensure a single `graphql` version is pulled, otherwise `graphql` itself will complain.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the examples in the linked denograts repository, then inspect schema.ts and the reported Deno import and module-remapping behavior. Compare scalar docblock discovery and the resolved graphql versions; done should mean the Deno setup has a defined, reproducible outcome for both reported issues.

Written by the indexing model from the issue text.

Assessment

Tech stack
deno, graphql, typescript
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.