Format and syntax
This guide explains what syntax you can use to format the documentation for NativeDB.
๐ข fully supported
๐ partially supported
๐ด not supported
Blocks | Markdown | Description | |
---|---|---|---|
Paragraph | ๐ขโโ | Some text | Basic block to show text. |
Code | ๐ขโโ |
| Useful to highlight arguments of a function.
Note: it doesn't support complex code block with a language (like |
URL | ๐ข | [label](https://) | You can add URL link with a label. URL must starts with |
Lists | ๐ โ |
| You can add ordered lists, unordered lists and tasks lists. In all cases, they will be visible as unordered lists using Note: you must not add newlines per item. It is not supported for now and formatting will not work as expected in NativeDB. Markdown example will look like this: - Item A - Item B - Item 1 - Item 2 - Item T - Item D |
Bold / Italic | ๐ดโ | **bold** *italic* | |
Headers | ๐ด | # H1 ## H2 ### H3 | |
Hint | ๐ด | {% hint %} {% endhint %} | |
Class reference | ๐ข | [ClassName] | Write the native name / alias name of a class between brackets ( |
Property reference | ๐ข | [this.prop] [ClassName.prop] | When documenting a class, you can reference its own properties using You can also reference properties of other classes using It must be surrounded by brackets ( |
Function reference | ๐ข | [this.GetStuff] [ClassName.SetStuff] | When documenting a class, you can reference its own functions using |
Enum / Bitfield reference | ๐ข | [Enum.Value] [Bitfield.Value] | You can reference value of an enum and value of a bitfield. |
Don't hesitate to look at other classes to see how the syntax is used, and how it looks like in NativeDB. If you are not sure, you can always come and ask on Discord.
Example
The following example is only made to show all possible syntax options. There is nothing related to the game:
Last updated