1f60197a15
Add `pipe queries`, which lists every Firestore query a project can issue: scope, collection, path pattern, filters with operators and value types, composites, orderBy, limit, cursors, realtime, aggregation, in-loop, plus a confidence and the reasons it is not exact. Receivers are matched by static type and cloud_firestore library URI, never by name. Queries are followed through chains, local variables (flow-insensitive with two cuts), fields, getters and one level of helper methods with arguments bound. An --adapter-config (YAML or JSON) maps declarative query APIs such as a server-side gateway onto the same schema. Inventory only: no rules, findings or baseline changes. Every emitted name is validated against a safe character set so no source text reaches the output.
10 lines
486 B
YAML
10 lines
486 B
YAML
# Rule fixtures are intentionally dependency-free standalone packages, so they
|
|
# must not inherit the repository analysis_options (which includes
|
|
# package:lints and would not resolve from here).
|
|
#
|
|
# They are deliberately NOT excluded from the repository analysis. Excluding
|
|
# them made any analyzer running in the repository context parse these files
|
|
# without resolving their imports, reporting phantom "undefined class" errors
|
|
# for perfectly valid fixtures.
|
|
analyzer:
|
|
exclude: []
|