Joined 17 years ago
In-between all those ephemeral agent sessions, spec, plan and design files, there is something that survives. The src/*.md files.
With Varar you can link small parts (cells) of those Markdown files to your code, so they stay in sync. So you (and agents) can find out what your system does without reading 300 million lines of code.
Full disclaimer: I am the guy who wrote Cucumber - that most people here hate. I eventually lost my love for that tool myself, but I did miss the ability to keep docs and code in sync. Hence Varar - a tool like that with fewer (different?) warts, for the agentic area.
It would be intersting to combine your «attention» metric with CRAP.
DocuSign customers buy trust.
It gets even better with elk layout - just prepend this frontmatter snippet to mermerd’s output:
---
config:
layout: elk
---
Postgraphile uses a naming convention for postgres functions to extend the GraphQL schema [1].
Do you have any plans to support a similar mechanism in pg_graphql?
I'm currently using Postgraphile[0], which uses Postgres' introspection API to discover the schema structure.
Would this still work with Hydra?