1
0
mirror of https://github.com/laurent22/joplin.git synced 2024-12-24 10:27:10 +02:00
joplin/ReactNativeClient/lib/joplin-renderer
2020-10-16 22:55:48 +01:00
..
assets Bump mermaid to 8.8.1 (#3853) 2020-10-09 21:42:16 +01:00
MdToHtml Mobile: Upgraded React Native to v0.63 2020-10-16 16:26:19 +01:00
tests
Tools
vendor
.gitignore
assetsToHeaders.js
defaultNoteStyle.js
HtmlToHtml.js Mobile: Upgraded React Native to v0.63 2020-10-16 16:26:19 +01:00
htmlUtils.js All: Security: Disallow EMBED tags to prevent XSS vulnerability 2020-09-06 19:29:42 +01:00
index.js
MarkupToHtml.js Mobile: Upgraded React Native to v0.63 2020-10-16 16:26:19 +01:00
MdToHtml.js Desktop: Fixes #3903: Header links with special characters were no longer working 2020-10-16 22:55:48 +01:00
noteStyle.js All: Add support for application plugins (#3257) 2020-10-09 18:35:46 +01:00
package-lock.json Desktop: Fixes #3903: Header links with special characters were no longer working 2020-10-16 22:55:48 +01:00
package.json Desktop: Fixes #3903: Header links with special characters were no longer working 2020-10-16 22:55:48 +01:00
pathUtils.js
publish.sh
README.md
stringUtils.js Desktop: Fixed GotoAnything rendering issue with HTML notes 2020-07-07 19:17:33 +01:00
urlUtils.js
utils.js Revert "Desktop, Mobile: Add support for media player for video and audio files" 2020-08-18 21:52:00 +01:00

Joplin Renderer

This is the renderer used by Joplin to render notes in Markdown or HTML format.

Installation

npm i -s joplin-renderer

Certain plugins require additional assets like CSS, fonts, etc. These assets are in the /assets directory and should be copied to wherever the application can find them at runtime.

Usage

const { MarkupToHtml } = require('joplin-renderer');

const options = {};

// The notes are rendered using the provided theme. The supported theme properties are in `defaultNoteStyle.js`
// and this is what is used if no theme is provided. A `theme` object can be provided to override default theme
// properties.
const theme = {};

const markdown = "Testing `MarkupToHtml` renderer";

const markupToHtml = new MarkupToHtml(options);
const result = await markupToHtml.render(MarkupToHtml.MARKUP_LANGUAGE_MARKDOWN, markdown, theme, options);

console.info('HTML:', result.html);
console.info('Plugin assets:', result.pluginAssets);

When calling render(), an object with the following properties is returned:

  • html: The rendered HTML code
  • pluginAssets: The assets required by the plugins

The assets need to be loaded by the calling application. For example this is how they are loaded in the Joplin desktop application:

function loadPluginAssets(assets) {
	for (let i = 0; i < assets.length; i++) {
		const asset = assets[i];

		if (asset.mime === 'text/css') {
			const link = document.createElement('link');
			link.rel = 'stylesheet';
			link.href = 'pluginAssets/' + asset.name;
			document.getElementById('joplin-container-styleContainer').appendChild(link);
		}
	}
}

Development

### Adding asset files

A plugin (or rule) can have any number of assets, such as CSS or font files, associated with it. To add an asset to a plugin, follow these steps:

  • Add the file under /assets/PLUGIN_NAME/your-asset-file.css
  • Register this file within the plugin using context.pluginAssets[PLUGIN_NAME] = [{ name: 'your-asset-file.css' }]

See katex.js for an example of how this is done.

Adding inline CSS

A plugin can ask for some CSS to be included inline in the rendered HTML. This is convenient as it means no extra file needs to be packaged. Use this syntax to do this:

context.pluginAssets[PLUGIN_NAME] = [
	{
		inline: true,
		text: ".my-css { background-color: 'green' }",
		mime: 'text/css',
	},
];