The Problem:
Currently, if you simply configure includedPaths: ['lib'], we likely analyze every Dart file found in lib.
This is "safe" but can lead to false positives (analyzing internal implementation classes that are not actually exported) or false negatives (missing re-export structures).
The Solution: Identify entry points and use them in PackageApiAnalyzer
- Typically lib/[package_name].dart.
- Sometimes there are multiple (e.g., package:flutter/material.dart, package:flutter/cupertino.dart).
- We should allow configuration of entry points, defaulting to the main library file.
The Problem:
Currently, if you simply configure includedPaths: ['lib'], we likely analyze every Dart file found in lib.
This is "safe" but can lead to false positives (analyzing internal implementation classes that are not actually exported) or false negatives (missing re-export structures).
The Solution: Identify entry points and use them in PackageApiAnalyzer