dart-lang / dart-lang/source_gen

Could non-build-related utilities be extracted to a separate package?

Open
#674 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Dart
Stars
494
Forks
115
Avg merge
12h 13m
Merged PRs (30d)
3

Description

Hello!

I was wondering if it was possible to extract various analyzer-based utils. They aren't tied to `build`, but are useful for quite a lot of analyzer projects.

For example, I was thinking of:

- TypeChecker
- Revivable

I find myself commonly having to fork those utils out of source_gen when I'm working on an analyzer-based project that doesn't use code generation (such as linters)

I don't mind making such package myself. But I figured I'd ask first about an official stance on the topic.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing TypeChecker and Revivable utilities in source_gen and how analyzer-based projects consume them. Determine the package boundaries and affected consumers before proposing an extraction; done means there is an agreed package design and migration path, rather than only an implementation of one utility.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.