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
359 B
Dart
10 lines
359 B
Dart
/// Collection names declared as constants, the way real apps centralise them.
|
|
const String kOrdersCollection = 'orders';
|
|
|
|
class Collections {
|
|
static const String auditTrail = 'auditTrail';
|
|
static const String stores = 'stores';
|
|
|
|
/// Final but not const: resolved from the declaration's literal initializer.
|
|
static final String reviews = 'reviews';
|
|
}
|