Why do i need a conditional type constraint when i already have the same constraint in the type arguments

This page summarizes the projects mentioned and recommended in the original post on /r/typescript

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • react-hook-form

    ๐Ÿ“‹ React Hooks for form state management and validation (Web + React Native)

  • Ah sorry, I somehow missed that error. Seems to be something funky with the types of useFieldArray which detect the array keys in the Control. They use a lot of recursive conditional types internally, and I can't figure out why adding an extra conditional type would make it do the right thing. I tried looking for a similar issue at https://github.com/react-hook-form/react-hook-form/issues/ but couldn't find anything. You should consider creating one if you can't figure it out.

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

    SurveyJS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts