rrousselGit / rrousselGit/analyzer_buffer
Consider creating a separate tool for lookups using the `package|identifier` syntax
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 20
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I like analyzer_buffer so far, but sometimes I want to use the useful syntax elsewhere for things like type checks,
For instance, it would be incredibly convenient to be able to produce a DartType out of this syntax, such as resolve('http', 'BaseRequest')
This can be especially nice for TypeCheckers, which seem to want either the exact uri or a direct dependency on the package for typeNamed
Basically, a sane means of doing type lookups extracted into it's own utility, or extension on LibraryElement .find perhaps?
All of this can allow me to look up a type, do some checks, and then do DartType.toCode() when I need it
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing analyzer_buffer’s existing package|identifier handling, then compare the needs of TypeCheckers, LibraryElement lookup, and DartType.toCode(). Clarify whether the result should be a separate utility or a LibraryElement.find extension, with resolution such as resolve('http', 'BaseRequest') serving as the completion criterion.
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
- 30/100