metadata-enforcer
We're going to spend the rest of our careers editing text files and metadata needs to become a first class citizen.
Compare these two metadata blocks:
Easy for us to see the difference. Same ideas, different names.
In a world where our job is to curate and organize and handle exceptions, PostgreSQL-level metadata enforcement is going to become more and more important.
Even more-so, I wonder if with Salesforce and Postgres, one of the main organizational value adds are actually constraints, referential integrity, and foreign key constraints?
That kind of makes sense, the same way that different divisions at Amazon have API boundaries.
What about your filesystem?
https://github.com/omarish/metadata-enforcer
Why not JSON Schema?
Because we want something very expressive. We want to define what is legal and what is illegal and these rules must be expressive, legible, turning complete, and done through code.
Version 1 used json-schema, but it wasn't indulgent enough.