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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Fix Version/s: 3.x
• Component/s: documentation
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Claus Ibsen
• Created: 13/Apr/22 09:21
• Updated: 03/Sep/22 12:23
• Resolved: 03/Sep/22 12:23

Description

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.