You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a helper function for rendering a Topics/SeeAlso section as HTML (#1382)
* Add a helper function for rendering a Topics/SeeAlso section as HTML
rdar://163326857
* Add more code comments and internal documentation comments
* Very slightly correct the test data
/// Creates a grouped section with a given name, for example "topics" or "see also" that describes and organizes groups of related API.
40
+
///
41
+
/// If each language representation of the API has its own task groups, pass the task groups for each language representation.
42
+
///
43
+
/// If the API has the _same_ task groups in all language representations, only pass the task groups for one language.
44
+
/// This produces a named section that doesn't hide any task groups for any of the languages (the same as if the symbol only had one language representation).
45
+
func groupedSection(named sectionName:String, groups taskGroups:[SourceLanguage:[TaskGroupInfo]])->[XMLNode]{
// TODO: As a future improvement we could diff the references and only mark them as language-specific if the group and reference doesn't appear in all languages.
/// Transforms the symbol name fragments into a `<code>` HTML element that represents a symbol's subheading.
137
+
///
138
+
/// When the renderer has a ``RenderGoal/richness`` goal, it creates one `<span>` HTML element per fragment that could be styled differently through CSS:
0 commit comments