Hey @ArnyminerZ ! A user reported an issue with the markdown handling (regrettably as a confidential issue), the problem is when a list is not started with the "-" character but with the "*" character, the whole line is interpreted as italic instead of being an unordered list.

I guess an additional check is necessary if there is an opening AND a closing character for "" or if there is only the "" character at the beginning of the line.

I might also have a look at it in the next days unless you're faster 😉

I have just added the Asterisk character to the check if it's a list. I'd say in the future the list handling also should allow formatting within the list items in the future, but I think that requires a bit of a structural change in the current method. So for now I'd leave it with that!

Currently there's no way of knowing the size of the image to be loaded, and InlineTextContent requires a Placeholder with a fixed size, so currently it's being set to

lastStyle.fontSize * 2  x  lastStyle.fontSize

The best way would be to load the image, take the size, and then load the InlineTextContent, however, this must be done asynchronously. Maybe adding a loading indicator or a placeholder from Accompanist for example would be a good solution.

Markdown should be able to display images. Right now everything is ready for this, since the module is developed in a column, so non-inline images can be simply added one after the other. For this, I believe the best option is to use a library like Glide or Coil.

When adding a header, the spaces after the # are conserved, and multiplied by each level, so for instance this:

## Title

Renders as:

···Title

Note: · are spaces

Jetbrains has released a library for parsing Markdown in Kotlin: JetBrains/Markdown.

This would be translated into basically a library rewrite, but would make parsing much more trusty, and adding new features much easier.

Bumps agp_version from 7.3.0 to 7.3.1. Updates com.android.application from 7.3.0 to 7.3.1

Updates com.android.library from 7.3.0 to 7.3.1

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Currently working:

• [x] Bold
• [x] Italic
• [x] Strikethrough
• [x] Code
• [ ] Links
• [x] Headers
• [ ] Lists
  • [ ] Unordered lists
  • [ ] Ordered lists
  • [ ] Checkboxes
• [ ] Images
  • [ ] Inline images
  • [ ] Block images
• [ ] Dividers

Would help on implementing #25

Hey @ArnyminerZ !

In jtx Board there was also the request to better support markdown in TextFields. Basically the idea is to show the text with the formatting but with the markdown indicators visible. In the best case those markdown indicators could have a lower opacity. The previously used library was actually doing that, so that feature got kind of lost now and it would be nice if we could add it again.

The TextField also takes a "TextFieldValue()" which accepts an annotated string. So maybe we can have a look if the function String.markdownAnnotated() can be adapted to do this. What do you think?

Bumps org.jetbrains.kotlin.android from 1.7.20 to 1.7.21.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.