Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Config Doc - IDE config metadata must be Markdown #43172

Open
gsmet opened this issue Sep 10, 2024 · 1 comment
Open

Config Doc - IDE config metadata must be Markdown #43172

gsmet opened this issue Sep 10, 2024 · 1 comment
Labels
area/config kind/enhancement New feature or request

Comments

@gsmet
Copy link
Member

gsmet commented Sep 10, 2024

Description

The config metadata for IDEs must be either plain text or Markdown. We will send Markdown.

We need a basic Asciidoc -> Markdown converter and a basic Javadoc -> Markdown converter.

The conversion will be made when we generate the metadata.

We might revisit when the Asciidoc is generated but let's be careful about backwards compatibility and make sure we ping the Camel team if we make changes.

Implementation ideas

No response
@gsmet gsmet added the kind/enhancement New feature or request label Sep 10, 2024
@quarkus-bot
Copy link

quarkus-bot bot commented Sep 10, 2024

/cc @radcortez (config)

@gsmet gsmet changed the title Config Doc - IDE config metata must be Markdown Config Doc - IDE config metadata must be Markdown Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/config kind/enhancement New feature or request
Projects
WG - Quarkus Config and IDEs
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gsmet