Chance Strickland
Chance Strickland
@rossipedia Can you confirm if this issue persists in 1.10+? I'm wondering if we may have fixed it in React Router after the 6.4 updates.
Following @davidsanchez96's lead, I still wanted the actual content to be rendered on both the server and the client, so this was my approach. ```js import React, { Component }...
Hey all! I'm back on the team and will be reviewing some old PRs, cleaning up the backlog in the coming weeks. This one's first on the list. Thanks for...
Also running into this. Splide uses `cloneNode` under the hood. I suspect the only way to solve this to cover for all events would be to rewrite the cloning feature...
One option that might work (have not explored too deeply) is to write your own `Clones` component (Splide component, not React component) and use `React.cloneElement`. Could also be a rabbit...
Sorry this has taken awhile. Adding to my backlog for some manual testing and then I'll merge ASAP. Locked conversation because "fix my issue" and "+1" comments are not helpful.
Looks like this has been fixed upstream in another commit
It would definitely be nice to fix any inconsistencies or incorrect use, but I'd prefer to separate the more opinionated use of `prettier-plugin-tailwindcss`. It makes the diffs a bit hard...
I think this is by design, though ideally our examples should be responsive. I think we should consider revisiting this. I'll add it to our backlog.
Hi there. I am also interested in forking/helping here. Let me know @alanef and @Hube2 if you two settled on a plan last year. Let me know how I might...