pf_app
Paul Trowbridge
424199c1aa
"Bucket" and "Segment" sit too close to the source data -- segment_new is an actual column here -- and a name collision would be worse than a confusing label: an expression named after an existing column shadows or rejects it rather than just reading ambiguously. pf_ prefixed like every other synthesised column, so they sort beside pf_bucket and pf_segment in the column list and read as belonging to the app. The old names are kept in the managed list so they are cleared from configs that still carry them. Without that they would sit in saved layouts forever, ordering by a rule nothing updates -- which is exactly what a stale Segment expression was already doing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| lib | ||
| public | ||
| routes | ||
| setup_sql | ||
| ui | ||
| .env.example | ||
| .gitignore | ||
| CLAUDE.md | ||
| install.sh | ||
| package-lock.json | ||
| package.json | ||
| PERSPECTIVE.md | ||
| pf_perspective_options.md | ||
| pf_spec.md | ||
| pf.sh | ||
| server.js | ||