Schema-risk
💡Idea❓Question
Hey everyone! Fellow nerdy tech person and aspiring developer here.
My team and I just open-sourced a new CLI tool called Schema-risk, and we’d love to get some eyes on it.
The Problem: We all know the sheer terror of a bad database migration silently breaking production.
The Solution: We built a package designed to catch destructive migrations before they ever execute.
The Ask: We are really focused on building this out from first principles and ensuring the underlying logic is rock-solid. If anyone has a few minutes to give our codebase a Socratic stress-test or offer a deep-dive critique on our architecture and state strategy, it would mean the world to us!
Check it out here: https://github.com/Keystones-Lab/Schema-risk
Let us know your thoughts, and please feel free to roast our code!
My team and I just open-sourced a new CLI tool called Schema-risk, and we’d love to get some eyes on it.
The Problem: We all know the sheer terror of a bad database migration silently breaking production.
The Solution: We built a package designed to catch destructive migrations before they ever execute.
The Ask: We are really focused on building this out from first principles and ensuring the underlying logic is rock-solid. If anyone has a few minutes to give our codebase a Socratic stress-test or offer a deep-dive critique on our architecture and state strategy, it would mean the world to us!
Check it out here: https://github.com/Keystones-Lab/Schema-risk
Let us know your thoughts, and please feel free to roast our code!
GitHub
Contribute to Keystones-Lab/Schema-risk development by creating an account on GitHub.
