Traveller
Traveller
@mertsincan @melloware I think this solution should be added to the documentation. Creating a variable number of tabs is a very common scenario.
> Interesting the showcase doesn't have the same behavior? https://primereact.org/dropdown/#filter Both `filter` and `editable` must be set at the same time for the problem to occur.
> We can already achieve the same results with the `custom` prop already, no? > > ```tsx > const Component = () => {} > > Component.craft => { >...
> > > We can already achieve the same results with the `custom` prop already, no? > > > ```tsx > > > const Component = () => {} >...
@prevwong Done. If any other changes need to be made, just let me know.
I could also wrap PrimeReact component with a `div` so that I only have to get the `ref` of the `div` and not the PrimeReact component. But this approach also...
Indeed, I do know how to get around this problem, i.e. write `drag(ref!)` instead. But I'm concerned that craft.js doesn't do anything special with null values, which could lead to...
> yarn install @Traveller23 Thanks, so all commands that use npm have to be changed to yarn, right?
This is the output on my machine: ``` $ yarn install ➤ YN0000: ┌ Resolution step ➤ YN0002: │ @craftjs/layers@workspace:packages/layers doesn't provide react-dom (pa69fb), requested by styled-components ➤ YN0002: │...
I found the solution: before running the example, you have to compile craft.js itself: ```bash cd ../.. yarn install yarn build cd examples/basic yarn install yarn start ``` There are...