dsherret / dsherret/ts-morph

Tracing diagnostics back to the original node

Open
#1,177 1 comment 0 reactions 0 assignees View on GitHub
question
Dominant language
TypeScript
Stars
6.2k
Forks
238
Avg merge
2m
Merged PRs (30d)
1

Description

Hi there!

I have a bit of an unusual requirement, I've been trying to find a way to keep track of the original nodes provided before transforming - and then use ts-morph to typecheck those statements in a different context/wrapper.

ts-morph has unlocked a huge part of the solution in that the bindings get updated on ast modification :raised_hands: .

What I'm trying to achieve is providing feedback to less-technical users (who can still swing some code) without them having to setup imports and all sorts of boilerplate.

I've tried to detail the requirement as best I can over here: https://github.com/OpenFn/kiini/issues/2

Any recommendations on how ts-morph could help or any complimentary projects would be really appreciated.

Contributor guide

Open the contributing guide

Research direction

Start by reading the linked OpenFn/kiini issue and the ts-morph behavior around AST modification and updated bindings. Determine whether tracing transformed nodes back to their originals is an existing capability or a scoped feature; this issue does not name files, tests, or a completion criterion.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.