I personally no longer have time/interest to maintain this library, for the simple reason that I am not using markdown in any of the projects I am currently (and for the foreseeable future) working on. This has probably been quite apparent in the lack of updates to the project recently, as well as sluggish response times to issues. Thank you to everyone who has contributed to the project thus far by way of PRs or issues, your work is much appreciated :)
Gladly, the library will live on and prosper. @zivester has been working on a fork of the project which is rather far ahead of this repository and has already fixed many of the issues that have been reported here. There are also plans to improve the library further with e.g. support for TypeScript.
What this means:
react-native-easy-markdown
, future changes will be published under the same npm package name1.2.0
of the library, and any version updates on npm thereafter will be based on the new repositoryReact Native Easy Markdown is a simple React Native component for rendering Markdown as native components, and it works equally well on both Android and iOS.
RNEM was created because other available libraries seemed to be somewhat inconsistent in how the parsed markdown is displayed, and they would render component trees filled with e.g. nested <Text/>
components where that was not necessary, which made styling difficult. RNEM also provides a possibility to supply your own render methods for certain components, such as images and links, so you can style and layout them however you wish.
For now, the following markdown is supported:
Any unsupported markdown will not crash your app, as it is simply ignored. If there is a more out-there use case you wish to have supported (such as code blocks etc.), the code is clean and simple to work on, and pull requests are most welcome. The project is stable and the current feature set should be enough for most use cases.
npm install --save react-native-easy-markdown
import Markdown from 'react-native-easy-markdown';
....
render() {
return(
<Markdown>
{
'# Why is markdown cool?\n\n' +
'* because it lets us do simple formatting **easily** \n' +
'* _without_ the need for complex CMS data structures \n' +
'* and you can outsource ~~your~~ work to the content creators! \n\n' +
'> This is a blockquote \n\n' +
'![We can add images!](http://placehold.it/300x300) \n' +
'[Or link to places](http://foobar.com) \n'
}
</Markdown>
);
}
Prop name | Description | Type | Default value |
---|---|---|---|
useDefaultStyles |
Whether to use default styles (see below) | boolean | true |
markdownStyles |
Override the default styles with your own (see style guide below) | object | {} |
parseInline |
Parse markdown inline, which is useful for simple markdown snippets intended to be displayed on a single line. (see here for details) | boolean | false |
debug |
Output logs that show the component tree that is being rendered based on the supplied markdown. | boolean | false |
style |
Style for the <Markdown/> component |
object | {} |
renderImage |
Custom renderer for images | function | none |
renderLink |
Custom renderer for links | function | none |
renderListBullet |
Custom rendered for list bullets | function | none |
If you need more control over how some of the components are rendered, you may provide the custom renderers outlined above like so:
renderImage(src, alt, title) {
return(
<MyImageComponent source={{uri: src}}/>
);
}
renderLink(href, title, children) {
return(
<MyTouchableThing onPress={() => console.log("Opening link: " + href)}>
{children}
</MyTouchableThing>
);
}
renderListBullet(ordered, index) {
return(
<View style={{width: 20, height: 20, backgroundColor: 'red}}/>
);
}
Notice the children
parameter passed to renderLink
, which contains whatever children would otherwise be rendered within the link. In the default implementation, those children will be rendered within a <TouchableOpacity/>
but this gives you the possibility to provide your own touchable component.
You can supply the component with your own markdownStyles
prop to override the defaults. Note that styles will be overridden only for the supplied properties, and other properties will use the default styles if useDefaultStyles
is true. Styles are applied to elements in order of specificity, so for example a strong text node would have both text
and strong
styles, in that order. Available styles are:
Style | RN component | Description |
---|---|---|
h1-h6 | <Text/> |
# Heading 1-6 |
text | <Text/> |
Base styles for all text components |
strong | <Text/> |
Additional styles for Strong text only |
em | <Text/> |
Additional styles for italic text only |
del | <Text/> |
Additional styles for |
u | <Text/> |
Additional styles for underline text only |
linkWrapper | <TouchableOpacity/> |
Touchable wrapper for links |
link | <Text/> |
Additional styles for text within links |
list | <View /> |
Wrapper around lists |
listItem | <View/> |
Wrapper around list items |
listItemContent | <View/> |
List item content wrapper, excluding the bullet/number |
listItemBullet | <View/> |
Bullet shown on unordered lists |
listItemNumber | <Text/> |
Number shown on ordered lists |
block | <View/> |
Wrapper around paragraphs |
blockQuote | <View/> |
Additional styles for paragraphs which are blockquotes |
imageWrapper | <View/> |
Wrapper around images, for easier layouting |
image | <Image/> |
Image component |
See default styles for reference.
1.2.0
1.1.9
1.1.8
1.1.7
1.1.3
1.1.2
1.1.1
1.1.0
<View>
within <Text>
is not supported on Android'1.0.5
1.0.4
1.0.3
This project is stable and reliable with the current feature set, and I did not want to add support for some of the more obscure markdown components now as they are not needed for my personal use cases and I did not want to add something that is not 100% working. I am more than happy to accept pull requests for any components that you would like to see included in this library.
Possible features to implement:
Copyright 2017 Juuso Lappalainen
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.