Closed callicles closed 3 weeks ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
company-landing | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Apr 25, 2024 1:07am |
framework-docs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Apr 25, 2024 1:07am |
framework-landing | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Apr 25, 2024 1:07am |
moose-product-analytics | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Apr 25, 2024 1:07am |
Re-organized the parsing and language centric part of the framework. We had
struct
that were used mixed between prisma and typescript parsing. As well as the code generation part in typescript. I separated the different languages in separate files and collocated all the code generation together.Introduced error handling from the blog post @phiSgr shared in here - it works really well to bubble up errors without loosing where they come from.
This adds support for the
Array
type in the ts definition and in the console all the way through the DB.I also noticed the SDK was generated twice I believe and removed one of the generations.
Removed some unnecessary
Arc
Changed the
Arity
property in our central data model to be onlyrequired
it is easier to manage all the types the same way instead of havingArray
as a separate one like prisma is doing.