After reviewing all major form libraries on the market, I identified a critical flaw: they require repeated definitions to build a form.
As we all know, the more times you define something, the higher the chance of introducing bugs.
In the above scenario, if we want to rename `firstName` to `name`, we’d need to update it in at least three places — significantly increasing code fragility.
That’s why I created Piying — a form library that achieves all the above functionality with just one definition
Whoa, this is truely cool! Defining metadata once and rendering anywhere—that's such a smart way to avoid those annoying inconsistencies and bugs that always pop up when you're managing forms. Seriously, kinda genius imo. How's the performance on larger, more complex forms?
Report
Piying's approach to reducing redundancies in form definitions is intriguing. I'm curious, how does it handle validation across different frameworks? Excited to see where this goes!
Report
Maker
@alexis_luo The component definition and logic part of piying are separated, so the logic part (including validation) can be used in any framework
Users only need to implement components under different frameworks
GPT-4o
Whoa, this is truely cool! Defining metadata once and rendering anywhere—that's such a smart way to avoid those annoying inconsistencies and bugs that always pop up when you're managing forms. Seriously, kinda genius imo. How's the performance on larger, more complex forms?
Piying's approach to reducing redundancies in form definitions is intriguing. I'm curious, how does it handle validation across different frameworks? Excited to see where this goes!
@alexis_luo The component definition and logic part of piying are separated, so the logic part (including validation) can be used in any framework
Users only need to implement components under different frameworks