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.
9 lines
258 B
YAML
9 lines
258 B
YAML
name: firestore_queries
|
|
description: >-
|
|
Fixture project for `pipe queries`. Depends on a hand-written cloud_firestore
|
|
skeleton under packages/, wired through a hand-written package_config.json.
|
|
version: 0.0.1
|
|
publish_to: none
|
|
|
|
environment:
|
|
sdk: ^3.0.0
|