Follow-up from #364 (the structured eql-manifest.json).
eql-codegen dump-catalog currently emits, per domain: segment / suffix / supported_ops. The Term enum (crates/eql-domains/src/term.rs) already knows each term's:
json_key() — hm / ob / bf / op
extractor() — eq_term / ord_term / match_term / ord_ope_term
ctor() — hmac_256 / ore_block_256 / bloom_filter / ope_cllw
Exposing the per-domain terms (with those names) in DomainEntry would:
Change: add a terms: Vec<TermInfo> (json_key + extractor + ctor) to DomainEntry in crates/eql-codegen/src/dump.rs, populated from d.terms + the Term accessors — a few lines; the data is all there. The manifest generator then maps it through.
Context: PR #364, cipherstash/docs#46.
Follow-up from #364 (the structured
eql-manifest.json).eql-codegen dump-catalogcurrently emits, per domain:segment/suffix/supported_ops. TheTermenum (crates/eql-domains/src/term.rs) already knows each term's:json_key()—hm/ob/bf/opextractor()—eq_term/ord_term/match_term/ord_ope_termctor()—hmac_256/ore_block_256/bloom_filter/ope_cllwExposing the per-domain
terms(with those names) inDomainEntrywould:eq_term/ord_term/match_term— these are real generated extractors, but doxygen doesn't capture them cleanly, so the catalog is the authoritative source for the names.Change: add a
terms: Vec<TermInfo>(json_key + extractor + ctor) toDomainEntryincrates/eql-codegen/src/dump.rs, populated fromd.terms+ theTermaccessors — a few lines; the data is all there. The manifest generator then maps it through.Context: PR #364, cipherstash/docs#46.