archview

Limitations

What v0.1 does not (yet) do.

archview is at v0.1. Known limitations:

  • Interface resolution. The CHA call graph is exact for a single implementation per interface. With multiple implementations, edges are over-approximated — unless a port or bus mediates them, which recovers the precise routing.
  • Route paths are literal. Group / router prefixes are not joined yet, so a route registered as /users under a /api group shows as /users, not /api/users.
  • Frameworks. gin, net/http and gRPC out of the box. Others need a custom extractor; GraphQL and WebSocket aren't covered yet.
  • dev-live only. The source tree and Go toolchain must be present at runtime; there is no baked artifact yet.
  • Inline closure handlers create an endpoint node but no link to a named handler (there is no function to point at).
  • Trivial helpers. A free function in a classified layer shows as a node; there is no trivial-helper filter yet.
  • No auth on /graph — guard it yourself in shared environments.

Most of these are addressed on the roadmap. If one is blocking you, open an issue.