doc(README): explain how to make inline custom renderers

Exilz · Exilz · commit 0847ded10f83 · 2018-01-02T17:51:01.000+01:00
diff --git a/README.md b/README.md
@@ -16,6 +16,7 @@ An iOS/Android pure javascript react-native component that renders your HTML int
     - [Demo](#demo)
     - [Creating custom renderers](#creating-custom-renderers)
         - [Custom HTML tags](#custom-html-tags)
+        - [Making your custom component block or inline](#making-your-custom-component-block-or-inline)
         - [Lists prefixes](#lists-prefixes)
     - [Styling](#styling)
     - [Images](#images)
@@ -126,6 +127,21 @@ Your renderers functions receive several arguments that will be very useful to m
 * `convertedCSSStyles` : conversion of the `style` attribute from CSS to react-native's stylesheet
 * `passProps` : various useful information : `groupInfo`, `parentTagName`, `parentIsText`...
 
+### Making your custom component block or inline
+
+By default, a custom renderer behaves like a block. So if you're rendering it between texts inside a `<p>`, you'll break your line.
+
+If you want it to be inline, you can slightly change the way you declare it, like this :
+
+```javascript
+renderers: {
+    mytag: { renderer: myTagRenderer, wrapper: 'Text' }, // new way, is inline
+    myothertag: myOtherTagRenderer // old regular way (still valid, behaves like a block)
+}
+```
+
+> Note : the only values for `wrapper` are `Text` or `View` (default). Those don't represent the `<View>` and `<Text>` component of react-native but are instead used in the parser to prevent crashes and properly render every HTML markup.
+
 ### Lists prefixes
 
 The default renderer of the `<ul>` and `<ol>` tags will either render a bullet or the count of your elements. If you wish to change this without having to re-write the whole list rendering implementation, you can use the `listsPrefixesRenderers` prop.
