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.
20 lines
427 B
JSON
20 lines
427 B
JSON
{
|
|
"configVersion": 2,
|
|
"packages": [
|
|
{
|
|
"name": "cloud_firestore",
|
|
"rootUri": "../packages/cloud_firestore/",
|
|
"packageUri": "lib/",
|
|
"languageVersion": "3.0"
|
|
},
|
|
{
|
|
"name": "firestore_queries",
|
|
"rootUri": "../",
|
|
"packageUri": "lib/",
|
|
"languageVersion": "3.0"
|
|
}
|
|
],
|
|
"generated": "2026-01-01T00:00:00.000Z",
|
|
"generator": "manual",
|
|
"generatorVersion": "1.0"
|
|
}
|