Offirmo
Error "Source and destination must not be the same" in move-sync on unicode normalization difference
Reopening this issue after reading https://github.com/jprichardson/node-fs-extra/issues/759 Could we fix this unicode normalization issue in the same way than case sensitivity ? Renaming a file into a different unicode normalization should...
Error "Source and destination must not be the same" in move-sync on unicode normalization difference
@manidlou sure. On a file system doing automatic unicode normalization: ```javascript const path = `voyage à Paris.jpg`.normalize('NFD') // user input = force normalization to an exotic one for demo purpose...
A very nice feature would be to allow a cache size of 1 to replicate `memoize-once` (i.e. leveraging immutability without hogging memory)
Precision: I'm using `StatefulToolTip` * tried changing the timeout = no effect * tried giving a different group to each tooltip = no effect
We devs are always complaining but sometimes it works... I got a successful setup using `ToolTip` and not `StatefulToolTip`. I have to manage some state myself though, so this bug...
This PR is trivial, 5 lines added to README. Anyone?
What I ended up implementing: ```jsx const { children, render, ...props } = this.props const ComponentOrFunctionOrAny = children || render || DEFAULT_CONTENT // is it a react component? if (ComponentOrFunctionOrAny.render...
I'm accidentally mutating some constant data object. I put Readonly everywhere, but the compiler didn't catch anything, precisely because the bug is mutating deep in the object... So that would...