Summary

Track detailed statistics for every Admin View, Site View, and Custom Admin View in your component — including field count, file output, compiled line totals, and blueprint dependencies — giving you insight into component complexity and maintenance scope.

🔍 What It Tracks

For each view (Admin, Site, or Custom Admin), JCB logs:

• 🧩 View type (Admin, Site, Custom Admin)
• 🧮 Total number of assigned fields
• 🗂️ Number of files generated during compile (PHP, XML, INI, etc.)
• 📏 Total line count output from compiled files
• 📎 Linked blueprints (e.g., templates, layouts, snippets)
• 📊 Presence of dynamic GETs or external data joins
• 🔐 ACL, routing, and controller flags (where applicable)

💡 Why It Matters

This per-view telemetry lets you:

• Identify which views are growing most in complexity
• Spot underutilized or bloated structures
• Track blueprint-to-output ratio (design vs. compile weight)
• Prioritize optimization or documentation efforts

🛠 How to Access

• During compilation, JCB logs stats per entity in the build report
• Viewable in the final compiler summary
• Exported in metadata (JSON) if enabled
• CLI output includes stats when compiling with --verbose or --log options

📘 Example Use Cases

• Analyze if a Site View has too many fields for frontend rendering
• See which Admin View produces the most code (and may need refactoring)
• Ensure that each Custom Admin View has expected layout or data logic
• Generate internal docs that show “which view does what”

✅ Benefits

• Transparent component architecture visibility
• Improved decision-making around refactor, testing, or training
• Data-backed insight for project contributors or auditors

Conclusion

Stats per Model/View transform JCB from a visual builder into a measurable dev platform. By surfacing granular data per view, you gain actionable insight into structure, complexity, and growth — helping you stay in control as your component evolves.