[
https://issues.apache.org/jira/browse/CAMEL-13920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Bednar reassigned CAMEL-13920:
----------------------------------
Component/s: (was: documentation)
tooling
Assignee: (was: Jan Bednar)
Remaining Estimate: (was: 0h)
Initial support added in PR3137. Keeping this Jira open, because in PR was
discussion about converting HTML javadocs to Ascidoctor, which is IMHO worth to
explore. With current solution we dont detect inline markups, e.g. links, these
are still stripped from javadoc. Solution proposed by [~zregvart] in PR will
allow full support, but there could be some non trivial changes in tooling.
> Find a way to propagate base markup syntax from javadoc to website
> ------------------------------------------------------------------
>
> Key: CAMEL-13920
> URL: https://issues.apache.org/jira/browse/CAMEL-13920
> Project: Camel
> Issue Type: Improvement
> Components: tooling
> Reporter: Jan Bednar
> Priority: Minor
> Time Spent: 20m
>
> HTML tags seems to be stripped out when creating json schema from javadoc.
> Can we include some of safe tags, or replace them with markup, or find some
> other way to propagate formating from javadoc to website?
> This can be seen specialy in [file
> component|https://camel.apache.org/components/latest/file-component.html] for
> readLock option.
> [Javadoc|https://github.com/apache/camel/blob/master/components/camel-file/src/main/java/org/apache/camel/component/file/GenericFileEndpoint.java#L842]
> for this option contains nice <li> list of allowed values, but on website
> (and also in file.json) are tags excluded. This tends to description, which
> is really hard to read on website.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
