Rinat

Thank you @ahmadnzr ! But I think it's not a solution. You'll need to do it on every update of the lib. I also found a solution using antd Form.Item...

closing due to https://github.com/scaffold-eth/create-eth/pull/58

Great start Shiv, thanks! Had the same todo in my notes, glad I don't need to write it since 100% you did it better 😄 > Make comments that actually...

found interesting point in Google style guide https://google.github.io/styleguide/tsguide.html#function-declarations. I like it but as I understand most people don't. If you're prefer arrow functions I think we need to add it...

I found that deployment protection can be changed/disabled only [per project](https://vercel.com/docs/security/deployment-protection#configuring-deployment-protection) , so one of the (bad) options is to go to project settings on vercel and disable it manually...

Current vercel output is ``` $ yarn vercel Vercel CLI 32.7.2 🔍 Inspect: https://vercel.com/rinsts-projects/my-awesome-se-2-app/21Q3p1RdcRfyHqggYzFQGUzquuYz [3s] ✅ Preview: https://my-awesome-se-2-46ppd28o7-rinsts-projects.vercel.app [3s] 📝 To deploy to production (my-awesome-se-2-app.vercel.app), run `vercel --prod` ``` So...

> In any case, I think it makes sense to rethink some of the props & display for the components. Maybe having a more standardized way of using the components...

> I think we have to draw the line somewhere... and just provide with the things that are obvious. If we are like: "should we add this component?" the answer...

> In any case, I think it makes sense to rethink some of the props & display for the components. Maybe having a more standardized way of using the components...