• Added customizable header colors:
  • Header levels have two new properties: override_font_color and font_color. When override_font_color is true, the headers will have its font color set to the font_color property. When override_font_color is false (default), headers will use the same font color as the rest of the text.
  • Implemented originally by halkeye (#8).
• Added support for task lists (#4):
  • Starting an unordered list item with [ ] or [x] will create a checkbox.
  • The checkboxes are clickable by default and emit a signal when clicked.
  • There's an option to disable cliking on checkboxes.
  • There's an option to customize the checkbox.
  • See the README file in the repo for more info.
• Added support for handling unhandled links (#10):
  • Added the unhandled_link_clicked signal, which is emitted when the MarkdownLabel node does not handle a click on a link automatically.
  • Added the assume_https_links property (default: true). If enabled, unrecognized links will be opened as HTTPS URLs (e.g. "example.com" will be opened as "https://example.com"). If disabled, unrecognized links will be left unhandled (emitting the unhandled_link_clicked signal). Ignored if automatic_links is disabled.
• Added support for custom syntax (#7):
  • Refactored the processing of all syntax elements into individual methods so they can be overridden if desired (_process_text_formatting_syntax(), _process_link_syntax(), etc.).
  • Added two empty methods: _preprocess_line() and _process_custom_syntax() which can be overridden to insert custom syntax.
• Fixed bug where a table could break all the following text.

• Implemented automatic handling of links:
  • Can be turned off with the automatic_links property.
  • Valid URLs and mails are opened with user default settings.
  • Headers are assigned an id following the same pattenr as Github-flavored markdown.
  • When clicked, links to that id make the label automatically scroll to their header (#3).
• The bbcode_enabled and text properties are now hidden on the editor (#1).

Needs some more testing and setting up for the Asset Library, but every desired feature is already implemented.