typing warning with Chakra UI's `Input` on sample-app

Running the sample-app example on this repository, which uses Chakra UI, seems to be giving a Type 'string' is not assignable to type 'never'. ts(2322) warning on the id property at app/components/FormInput.jsx:30. Including the snippet here for easier reading:

// ...

  return (
    <>
      <FormControl isInvalid={!!error} isRequired={isRequired}>
        <FormLabel htmlFor={name}>{label}</FormLabel>
        <Input
          {...getInputProps({
            id: name,
            ...rest,
          })}
        />
        {error && <FormErrorMessage>{error}</FormErrorMessage>}
      </FormControl>
    </>
  );

Now, everything still seems to work fine and my experience with Chakra UI is none so I might be missing something obvious, but seeing as this is an official example I’m wondering if there’s anything to be done about it…

[airjp73]

@rmobis, I’m going to end up reverting that fix, I think. I’m working on adding to getInputProps and running into issues with the current typing. I’ve tried the old typing with other component libraries and Chakra seems to be the only one with this issue.

For an alternate fix, you can get the correct functionality without as never or as any is by supplying the generic directly.

import { Input, InputProps } from '@chakra-ui/react';

<Input {...getInputProps<InputProps>({ id: name, ...rest })} />

[airjp73]

I found a solution and will publish it. Somehow switching from Omit<T, 'defaultValue' | 'name'> to T & { defaultValue?: never, name?: never } fixed it. One downside to this is that defaultValue and name show up as autocomplete options, but it still prevents you from setting them.