Explore tweets about #react.fragment on Twitter
@tomiwa_of_mars @itisteacher or you can just use react fragment tag (I prefer short version which is just an empty tag) instead of div to avoid #divitis and to achieve good HTML semantics. You also can still use <a> for links
0
0
0
#WebDev
@NULifeSFBA In React, we usually use div to wrap and group content on the page inside of a single React Component. But if we use Flex, the outside div won't work properly. React Fragment could perfectly solve this. We can wrap our ContentComponent in React Fragments.
0
0
0
✅ Got @tailwindui working!
Took me a while to figure out how to convert HTML to JSX, but this @code (how did they get that handle??) plugin handled it perfectly. Just needed to add <React.Fragment> around the code to get it to work.
https://t.co/lcu9jPBTn0 https://t.co/5SAOpzwzZV
1
0
3
So, how do you explain to a PM who contracted out a VERY IMPORTANT project to a "React Expert" that our company literally got fucked over with an app which is mainly JS DOM manipulation re: 2005 in a React.Fragment container?
1
0
0
Ever wonder the difference between :active and :focus or <> and React Fragment? This neat website has the answers 👀 👀 https://t.co/XKcJsbkUzQ
0
2
8
Day 52:
☑️ Working on react exercises that use Wikipedia API and
created accordion app using useEffect and useState.
☑️ Learnt about the XSS attacks, React fragment the
difference between rem and em.
#151daysofcode #react #javscript
1
1
5
Breaking down #React 👇
🔸Adjacent JSX elements must be wrapped inside an enclosing tag. Don't use a wrapping <div> . We can do better.
🔸 Instead we can use React.Fragment to group children without adding extra nodes to DOM.
🔸 This can be simplified using <> syntax. https://t.co/oAYKiHH1q1
2
1
6
@BenLesh Just because you export one of the things as default, doesn't mean you can't export the other things as is. React is actually doing this AFAIK.
import React, { Fragment } from 'react'
0
0
0
<React.Fragment /> is love , if only everyone can understand it.
#100DaysofCode #100DaysOfCode #WomenWhoCode #React #js #javascript30 #FullstackDevJs #CodeNewbies #Coding #DEVCommunity #DevCommunityIN
0
8
5
React.Fragment を Layout で使うと、最後のモジュールが2重に出力されるっぽいんだけど、何が悪いのだろう👀
function Layout({ children }) {
return (
<React.Fragment>
<Header />
<main>{children}</main>
<Footer /> ← 2つ出る
</React.Fragment>
)
}
0
0
0
久しぶりにReactに触れてみているマン。ルートの不要なdiv要素がいらなくなったという噂を聞いていたけれど、結局React.Fragment要素（的な）のは必要なのね👀
0
0
0
@kentcdodds The best solution currently looks to be wrapping children with React.Fragment. Should be unnecessary!
https://t.co/MgTNAZRZjF
0
0
0
Just learned that React sees this fragment "<>" as a "Parent Element" and if you want to silence the "child doesn't have key" warning you have to use the full "React.Fragment" and put the key on that.
.map(item => (
<>
<Item key={https://t.co/OjsCc93MDw} />
2
0
6