#reactmarkdown search results

Using `<Typography>...</Typography>` (@MaterialUI) around `<ReactMarkdown />` (#ReactMarkdown) results in `<p>` nested into another `<p>` when rendered ...which is not a valid #HTML! :[ I wonder how do I work around it. *sigh* Integration is giving me unnecessary problems.

n0ther_guy's tweet image. Using `&amp;lt;Typography&amp;gt;...&amp;lt;/Typography&amp;gt;` (@MaterialUI) around `&amp;lt;ReactMarkdown /&amp;gt;` (#ReactMarkdown) results in `&amp;lt;p&amp;gt;` nested into another `&amp;lt;p&amp;gt;` when rendered ...which is not a valid #HTML! :[

I wonder how do I work around it.

*sigh* Integration is giving me unnecessary problems.
n0ther_guy's tweet image. Using `&amp;lt;Typography&amp;gt;...&amp;lt;/Typography&amp;gt;` (@MaterialUI) around `&amp;lt;ReactMarkdown /&amp;gt;` (#ReactMarkdown) results in `&amp;lt;p&amp;gt;` nested into another `&amp;lt;p&amp;gt;` when rendered ...which is not a valid #HTML! :[

I wonder how do I work around it.

*sigh* Integration is giving me unnecessary problems.
n0ther_guy's tweet image. Using `&amp;lt;Typography&amp;gt;...&amp;lt;/Typography&amp;gt;` (@MaterialUI) around `&amp;lt;ReactMarkdown /&amp;gt;` (#ReactMarkdown) results in `&amp;lt;p&amp;gt;` nested into another `&amp;lt;p&amp;gt;` when rendered ...which is not a valid #HTML! :[

I wonder how do I work around it.

*sigh* Integration is giving me unnecessary problems.

Trying out #ReactMarkdown in my app. Keeping fingers crossed!


#reactmarkdown does rock! it makes up for #reactrouter4 loopiness lol.


Me: *spends weeks building custom AI response outputs with react-markdown everywhere* @vercel: "Hold my beer" *quietly drops Streamdown (streamdown.ai) - the perfect solution I didn't know I needed* The irony is real. Also, the admiration. 🫡 #ReactMarkdown


So this makes some data have two formats instead of one because i wanted to have capability of letting users using the editor with markdown. I then render the contents which only have markdown format using #reactmarkdown. Those with two formats, i use render the html in a div.


Rendering markdown made easy with react-markdown in ReactJS and NextJS web APPs via dev.to/shareef/render… #markdown #webdev #reactmarkdown #nextjs


Me: *spends weeks building custom AI response outputs with react-markdown everywhere* @vercel: "Hold my beer" *quietly drops Streamdown (streamdown.ai) - the perfect solution I didn't know I needed* The irony is real. Also, the admiration. 🫡 #ReactMarkdown


So this makes some data have two formats instead of one because i wanted to have capability of letting users using the editor with markdown. I then render the contents which only have markdown format using #reactmarkdown. Those with two formats, i use render the html in a div.


Rendering markdown made easy with react-markdown in ReactJS and NextJS web APPs via dev.to/shareef/render… #markdown #webdev #reactmarkdown #nextjs


Using `<Typography>...</Typography>` (@MaterialUI) around `<ReactMarkdown />` (#ReactMarkdown) results in `<p>` nested into another `<p>` when rendered ...which is not a valid #HTML! :[ I wonder how do I work around it. *sigh* Integration is giving me unnecessary problems.

n0ther_guy's tweet image. Using `&amp;lt;Typography&amp;gt;...&amp;lt;/Typography&amp;gt;` (@MaterialUI) around `&amp;lt;ReactMarkdown /&amp;gt;` (#ReactMarkdown) results in `&amp;lt;p&amp;gt;` nested into another `&amp;lt;p&amp;gt;` when rendered ...which is not a valid #HTML! :[

I wonder how do I work around it.

*sigh* Integration is giving me unnecessary problems.
n0ther_guy's tweet image. Using `&amp;lt;Typography&amp;gt;...&amp;lt;/Typography&amp;gt;` (@MaterialUI) around `&amp;lt;ReactMarkdown /&amp;gt;` (#ReactMarkdown) results in `&amp;lt;p&amp;gt;` nested into another `&amp;lt;p&amp;gt;` when rendered ...which is not a valid #HTML! :[

I wonder how do I work around it.

*sigh* Integration is giving me unnecessary problems.
n0ther_guy's tweet image. Using `&amp;lt;Typography&amp;gt;...&amp;lt;/Typography&amp;gt;` (@MaterialUI) around `&amp;lt;ReactMarkdown /&amp;gt;` (#ReactMarkdown) results in `&amp;lt;p&amp;gt;` nested into another `&amp;lt;p&amp;gt;` when rendered ...which is not a valid #HTML! :[

I wonder how do I work around it.

*sigh* Integration is giving me unnecessary problems.

#reactmarkdown does rock! it makes up for #reactrouter4 loopiness lol.


Trying out #ReactMarkdown in my app. Keeping fingers crossed!


No results for "#reactmarkdown"

Using `<Typography>...</Typography>` (@MaterialUI) around `<ReactMarkdown />` (#ReactMarkdown) results in `<p>` nested into another `<p>` when rendered ...which is not a valid #HTML! :[ I wonder how do I work around it. *sigh* Integration is giving me unnecessary problems.

n0ther_guy's tweet image. Using `&amp;lt;Typography&amp;gt;...&amp;lt;/Typography&amp;gt;` (@MaterialUI) around `&amp;lt;ReactMarkdown /&amp;gt;` (#ReactMarkdown) results in `&amp;lt;p&amp;gt;` nested into another `&amp;lt;p&amp;gt;` when rendered ...which is not a valid #HTML! :[

I wonder how do I work around it.

*sigh* Integration is giving me unnecessary problems.
n0ther_guy's tweet image. Using `&amp;lt;Typography&amp;gt;...&amp;lt;/Typography&amp;gt;` (@MaterialUI) around `&amp;lt;ReactMarkdown /&amp;gt;` (#ReactMarkdown) results in `&amp;lt;p&amp;gt;` nested into another `&amp;lt;p&amp;gt;` when rendered ...which is not a valid #HTML! :[

I wonder how do I work around it.

*sigh* Integration is giving me unnecessary problems.
n0ther_guy's tweet image. Using `&amp;lt;Typography&amp;gt;...&amp;lt;/Typography&amp;gt;` (@MaterialUI) around `&amp;lt;ReactMarkdown /&amp;gt;` (#ReactMarkdown) results in `&amp;lt;p&amp;gt;` nested into another `&amp;lt;p&amp;gt;` when rendered ...which is not a valid #HTML! :[

I wonder how do I work around it.

*sigh* Integration is giving me unnecessary problems.

Loading...

Something went wrong.


Something went wrong.


United States Trends