Bug 58926 - TableSectionBase missing diagram
Summary: TableSectionBase missing diagram
Status: NEW
Alias: None
Product: Documentation
Classification: Xamarin
Component: Multi-Platform ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: bryan costanich
Depends on:
Reported: 2017-08-21 13:58 UTC by Edward Brey
Modified: 2017-08-21 14:02 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 58926 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Edward Brey 2017-08-21 13:58:14 UTC
The docs for Xamarin.Forms.TableSectionBase<T> Class say, "Subtypes of TableSectionBase`1 are TableSection and TableRoot, as shown in the following diagram:", but there is no diagram.

Comment 1 Edward Brey 2017-08-21 14:02:46 UTC
Bigger picture, the class diagram isn't essential. More important is the conceptual relationship between the classes, and a description of when and how you'd use each.