Vadim Demedes
Vadim Demedes
Hm, that sounds like an issue with your configuration? This package doesn't do anything fancy or custom regarding exports, it's just `export default` transpiled via TS. Does something like `import...
I can't reproduce this. Could you write how to spot this behavior?
Hm yeah, I think escape sequences should be ignored in `useInput`. Going to mark this one as a bug.
This component does export `Item` type, there's a mistake in your example: ```ts export function ChoicesComponent({ itemComponent = Item, items, onSubmit }: Props) { ``` `itemComponent = Item` means `Item`...
Hm, what would be a solution for this?
I think you can solve this via: ``` import {FC, ComponentType} from 'react'; import {ItemProps} from 'ink-select-input'; interface Props { itemComponent: ComponentType } const MyCustomComponent: FC = ({itemComponent}) => ...;...
Tried reproducing it with this, but didn't see that error: ```jsx const React = require('react') const {Box, Text, render} = require('ink') const TextInput = require('.').default const Example = () =>...
Hey @dmonad, I know it's an old PR, but could you please let us know if this is the right direction to take for supporting overlapping ProseMirror marks?
Sorry for huge delay. I assume you would be able to use enzyme or a similar library to test the component tree?
Hm, wouldn't it be less hacky to expose some sort of API to traverse/assert React nodes instead? I didn't mean exposing Yoga or Ink nodes before, but React tree itself....