3 ms·

Sounds like graphQL except it’s actually decent. Must have been nice.

• vidarh 3y ago
  It had warts, and I'm vaguely tempted to make another, cleaner, attempt at it with the assorted lessons learned - I don't work there any more and the parent company has ditched all the code, and so while I can't release that code, writing a new version from scratch wouldn't compete with anything they do. Not top of my list at the moment, though.
  • srcreigh 3y ago
    Any sufficiently powerful API could be misused anyway. Don’t have any regrets for not adding another one into the mix.
    • vidarh 3y ago
      For it to make sense, it'd need to be the full package, with UI components. The nice thing was being able to annotate the model and get a "good enough for an MVP" CRUD ui out of it that'd significantly beat a generic database browser; not just the API. Unfortunately that's also accordingly more work. I need a project that'll actually need it first...