You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The upstream PR targets a different structure (pnpm, @emulators/* scope, a apps/web docs site, @emulators/core as a workspace dep), so it could not be merged directly. The service core was re-homed to match this fork instead.
What's included
New @pleaseai/emulate-linear package under packages/linear/
bun export condition, @emulators/core@^0.6.0 + graphql deps, tsgo type-check
Registered linear in the CLI service registry (packages/emulate) + dependency wiring
Source adapted to fork's core 0.6.0
Hono type sourced from @emulators/core (no direct hono dep)
explicit 405 handlers for non-POST /graphql (core's router has no all)
tests converted from vitest → bun:test using createServer
Docs: skills/linear/SKILL.md, package README, and root README entries adapted to fork CLI usage (bun packages/emulate/dist/index.js --service linear)
Excluded from the upstream PR
apps/web/* docs site, pnpm-lock.yaml, and emulate.config.example.yaml — these don't exist in this fork.
Surface (read-only GraphQL)
POST /graphql with schema introspection, PAT auth (Authorization: <api_key>), Relay-style pagination, and query resolvers for Issue, Project, Team, User, Organization, Label, and WorkflowState.
Verification
✅ Monorepo build (7) · type-check (13) · test (13, linear 26 pass) · lint
✅ End-to-end: emulate list shows linear; service boots and answers GraphQL queries; missing auth returns 401
Port vercel-labs/emulate#91 (Phase 1 Linear emulator) to the @pleaseai
fork conventions:
- New @pleaseai/emulate-linear package under packages/linear/ (bun export
condition, @emulators/core ^0.6.0 + graphql dependency, tsgo type-check)
- Register linear in the CLI service registry (packages/emulate)
- bun:test instead of vitest; explicit 405 handlers for non-POST /graphql
since core's router has no `all`; Hono type sourced from @emulators/core
- skills/linear/SKILL.md and README entries adapted to fork CLI usage
Read-only GraphQL: issues, projects, teams, users, organizations, labels,
and workflow states with Relay-style pagination. 26 tests pass.
Original PR: vercel-labs/emulate#91 by @mvanhorn
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
The port of the Linear GraphQL API emulator is largely complete in terms of feature set, but several implementation details pose risks to its reliability. Most critically, the store collections are missing indices for foreign keys (e.g., organization_id, assignee_id); without these, the @emulators/core framework will fail to resolve relationships between entities, effectively breaking graph traversal.
Codacy analysis indicates the PR is not up to standards, primarily due to code duplication in entity resolvers and unsafe property access. Furthermore, 'packages/linear/src/resolvers.ts' and 'packages/linear/src/index.ts' are identified as complex files with insufficient test coverage. While 405 Method Not Allowed handlers were implemented as requested in the acceptance criteria, they currently lack automated verification. These issues, particularly the indexing logic, should be addressed prior to merging to ensure the emulator functions as intended.
About this PR
There is a systemic pattern of code duplication across entity resolvers (Organization, User, Team, etc.) regarding standard field mapping. Centralizing this logic into a helper function would improve maintainability.
Test suggestions
Execute a valid GraphQL query for an issue by ID and identifier
Perform GraphQL schema introspection
Verify authentication using a raw PAT in the Authorization header
Verify authentication using a Bearer token in the Authorization header
Verify that missing or invalid authentication returns a 401 with a Linear-compatible error code
Test forward pagination using 'first' and 'after'
Test backward pagination using 'last' and 'before'
Verify that GET, PUT, PATCH, and DELETE requests to /graphql return a 405 Method Not Allowed error
Validate that GraphQL validation errors return a 200 OK with an errors array containing extensions.code
Automate verification of relational traversals (e.g., fetching a team's issues) to ensure store indices are working
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that GET, PUT, PATCH, and DELETE requests to /graphql return a 405 Method Not Allowed error
2. Automate verification of relational traversals (e.g., fetching a team's issues) to ensure store indices are working
- store: index organization_id (users/teams), lead_id (projects),
state_id/assignee_id/creator_id (issues) — all fields queried via findBy,
per the fork's store convention (avoids full-scan fallback)
- resolvers: use Object.hasOwn for directValue field access (own-property only)
- tests: cover 405 responses for non-POST methods on /graphql
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
Summary
Ports vercel-labs/emulate#91 (Phase 1 Linear emulator, by @mvanhorn) into this fork's conventions.
The upstream PR targets a different structure (pnpm,
@emulators/*scope, aapps/webdocs site,@emulators/coreas a workspace dep), so it could not be merged directly. The service core was re-homed to match this fork instead.What's included
@pleaseai/emulate-linearpackage underpackages/linear/@emulators/core@^0.6.0+graphqldeps,tsgotype-checklinearin the CLI service registry (packages/emulate) + dependency wiringHonotype sourced from@emulators/core(no directhonodep)405handlers for non-POST/graphql(core's router has noall)vitest→bun:testusingcreateServerif,node:bufferimport)skills/linear/SKILL.md, package README, and root README entries adapted to fork CLI usage (bun packages/emulate/dist/index.js --service linear)Excluded from the upstream PR
apps/web/*docs site,pnpm-lock.yaml, andemulate.config.example.yaml— these don't exist in this fork.Surface (read-only GraphQL)
POST /graphqlwith schema introspection, PAT auth (Authorization: <api_key>), Relay-style pagination, and query resolvers for Issue, Project, Team, User, Organization, Label, and WorkflowState.Verification
build(7) ·type-check(13) ·test(13, linear 26 pass) ·lintemulate listshows linear; service boots and answers GraphQL queries; missing auth returns401Follow-up work: mutations, webhooks, OAuth 2.0, inspector UI.