About this issue

You can make images using remote links (https, http), but you can't specify local path to render local image i've tried ./path/img.png, path/img.png, file:///path/img.png but none worked so far and by the looks of imagePainter in ImagePainterProvider - it won't, because it fetches image always through http

Credited project could use local image paths

Details

• [multiplatform-markdown-renderer 0.4.0]
• [Desktop]
• [Compose 1.1.1]
• [Gradle 7.2]
• [JDK 17]

This PR proposes an optional color override for the markdown text. It allows applications that do not use MaterialTheme to still be able to set their text color. The default color is still MaterialTheme.color.onBackground

Also add the ability to specify colors per node-type via an optional map. This is probably a naive approach, I just wanted to get the idea out there.

Multiplatform For multiplatform projects specify this single dependency:

dependencies { implementation("com.mikepenz:multiplatform-markdown-renderer:0.1.0") }

Use Markdown("", Modifier.fillMaxSize())

Exception in thread "AWT-EventQueue-0" java.lang.IncompatibleClassChangeError: Found class androidx.compose.runtime.Composer, but interface was expected at com.mikepenz.markdown.MarkdownKt.Markdown(Markdown.kt:51)

About this issue

Given a link that looks like this: [https://example.com](https://github.com/mikepenz), the library renders nothing on screen. Expected behavior would be for it to show https://example.com.

Details

• Used library version: 0.1.0
• Used platform: Compose Desktop
• Used support library version: 1.0.0-alpha4-build398
• Used gradle build tools version: Gradle 7.2
• Used tooling / Android Studio version: IntelliJ IDEA 2021.3 EAP, reproducible without an IDE.
• Other used libraries, potential conflicting libraries: None, this is reproducible in the Compose Desktop sample.

Checklist

• [x] Searched for similar issues
• [x] Checked out the sample application
• [x] Read the README
• [x] Checked out the CHANGELOG
• [x] Read the FAQ
• [x] Checked out the MIGRATION GUIDE

About this issue

The CommonMark spec for it can be found here.

Changing the text rendered by the compose-desktop sample to either of the ones given below reproduces the issue.

### Getting Started

To get started you will need GPG on your computer to create a new key pair. 

Usually I go with the [GPG Suite][1], which offers a nice UI to manage your keys. (You may want to use advanced installation to only install the parts you need)
But you can also use any other solution to create your key pair.

![Image](https://avatars.githubusercontent.com/u/1476232?v=4)

After installing GPG Suite (or your prefered solution) first create a new key.

Using GPG Suite, start the GPG Keychain, which shows all current known GPG keys on your system.

Click on `New` and you will be offered to enter your name, e-mail and password. Ensure to pick a secure password to protect your key. 
[1]: https://gpgtools.org/

### Getting Started

To get started you will need GPG on your computer to create a new key pair. 

Usually I go with the [GPG Suite], which offers a nice UI to manage your keys. (You may want to use advanced installation to only install the parts you need)
But you can also use any other solution to create your key pair.

![Image](https://avatars.githubusercontent.com/u/1476232?v=4)

After installing GPG Suite (or your prefered solution) first create a new key.

Using GPG Suite, start the GPG Keychain, which shows all current known GPG keys on your system.

Click on `New` and you will be offered to enter your name, e-mail and password. Ensure to pick a secure password to protect your key. 
[GPG Suite]: https://gpgtools.org/

Details

• Used library version: 0.1.0
• Used platform: Compose Desktop
• Used support library version: 1.0.0-alpha4-build398
• Used gradle build tools version: Gradle 7.2
• Used tooling / Android Studio version: IntelliJ IDEA 2021.3 EAP, reproducible without an IDE.
• Other used libraries, potential conflicting libraries: None, this is reproducible in the Compose Desktop sample.

Checklist

• [x] Searched for similar issues
• [x] Checked out the sample application
• [x] Read the README
• [x] Checked out the CHANGELOG
• [x] Read the FAQ
• [x] Checked out the MIGRATION GUIDE

The 0.0.1release of the library was published with AGP 7.1.0-alpha13 which presents the artifact as incompatible when trying to consume it in a project using the newly released AGP 7.2.0-alpha01.

Here is a Gradle build scan detailing the failure encountered, and the source code to reproduce the failure can be found here. Building the android module of the linked project is enough to reproduce the bug.

• upgrade dependencies to the major new versions

    const val compose = "1.2.1"
    const val composeCompiler = "1.2.0"
    const val activityCompose = "1.5.1"
    kotlin = 1.7.0
    dokka = 1.7.10
    aboutLibraries = 10.4.0
    compose-jb = 1.2.0-alpha01-dev755

About this issue

What u think about create data class Typography/Color with text style for all item in markdown? And I think great point for custom padding

• upgrade dependencies to newer version

classpath("com.android.tools.build:gradle:7.2.1")
classpath("io.gitlab.arturbosch.detekt:detekt-gradle-plugin:1.20.0")
classpath("com.mikepenz.aboutlibraries.plugin:aboutlibraries-plugin:10.3.1")

const val material = "1.6.1"

• introduce new bullet list handling (use circle ascii character by default)
• offer custom local handlers to adjust the behavior for ordered and unordered list
  • FIX #41

Based off the code from what I can tell passing a custom MarkdownColors with the text color set should render things in text color. Bullet lists however always stay black.

This is an POC for #57 Its just an example to show how custom components can be used.

The handleElement function does not handle the rendering itself. It delegates to the configured components.

The changes in existing code should be backward compatible.

Whats included:

Add a configuration to allow custom components. The default delegates to the current implementation (see CurrentComponentsBridge)

About this issue

It would be nice if I could use my own components for rendering.

Use Cases:

• Render only a subset of components (e.g. only headings for a table of contents)
• Decorate a component (e.g. add a "copy to clipboard" button to code)
• Add custom logic (e.g. resolve relative URLs in links anmd images)

About this issue

• Briefly describe the issue

• How can the issue be reproduced / sample code Hi, I'm using Compose for Web as a kotlin("js") project and I installed the library in multiplatform, but I still can't use it in my project, I'm in Compose 1.2.0-apha01-dev753 using Kotlin 1.7.0 with Gradle 7.5.0 and the library in 0.6.1 with Intellij 2022.2.

Checklist

• [X] Searched for similar issues
• [X] Checked out the sample application
• [X] Read the README
• [X] Checked out the CHANGELOG
• [X] Read the FAQ
• [X] Checked out the MIGRATION GUIDE

About this issue

ASTNode.handleElement for  section are handled by a paragraph and not MarkdownElementTypes.IMAGE This is causing images to appear with a fixed size of 180.dp since Placeholders aren't supporting flexibility here.

Details

• [ ]  0.2.4
• [ ] Android, Desktop(Linux)
• [ ] 7.0.4
• [ ] IDEA-U