[jira] [Resolved] (CAMEL-17960) camel documentation - Separate component/endpoint options table with inherited vs its own

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-17960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-17960.
---------------------------------
    Resolution: Won't Fix

> camel documentation - Separate component/endpoint options table with inherited vs its own
> -----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-17960
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17960
>             Project: Camel
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 3.x
>
>
> The camel docs for components have big tables with options. Because each component/endpoint inherit some standard options then those tables can be big - especially for scheduled polling based.
> Maybe we should have a divider or something in the table so the common options are listed below the specific ones in the top.
> table start
> - component special options
> - inherited options here
> table end
> That can help users to more quickly find the options that are specific for the component and which 90% of the time they need to use/configure first.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)