Nx adapter: map files and test files to Nx projects from `nx graph`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 56/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- node.js, typescript
Research direction
Start with the adapter interface in src/repo/adapters/types.ts and trace how repository adapters assign test files and package dependencies. Check how verify and observe --no-send handle repository analysis before deciding where the Nx graph can be used safely. Add a small Nx fixture with one inferred and one explicit test target; done means ownership and dependency edges are covered, and graph failures follow the stated blocker behavior.
Written by the indexing model from the issue text.
Description
Part of #111.
- Detect Nx:
nx.jsonat the root andnxin the root manifest. - Run the repository's own Nx:
node_modules/.bin/nx graph --file=<tmp>.jsonwithNX_DAEMON=false,NX_NO_CLOUD=trueand a timeout. Plugin-inferred targets (@nx/vite/plugin,@nx/jest/plugin) only exist after Nx evaluates its plugins, so readingproject.jsonalone would miss them. - Running Nx executes plugin code.
verifymay do it.observe --no-sendshould use the graph only from a cache for the same tree, or with an explicit flag. - Contribute through the adapter interface (
src/repo/adapters/types.ts):- project ownership of test files (
testPackages, deepest project root wins); implicitDependenciesand Nx-detected project dependencies as package-level edges.
- project ownership of test files (
- Blockers: Nx fails to produce a graph (global); a target with an executor DiffCI can't narrow (scoped to that project).
- Fixture: a small Nx workspace with one inferred and one explicit
testtarget.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 4
- Avg merge
- 18h 41m
- Merged PRs (30d)
- 48
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DiffCI/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at randomPossibly taken @FredApps claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Agent tools: changed_files lists only the new path of a renamed filePossibly taken @FredApps claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
adapter good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
agent-ready area: ui-server priority: p3 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
schlessera/brain-kit#4249 ·
Maintainers usually reply within 1 day
-
documentation tool triaged
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
can1357/oh-my-pi#19608 · 2 comments ·
Maintainers usually reply within 1 day
-
dependencies tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bcgov/nr-waste-plus#1549 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·