If a component has a child content parameter that is a RenderFragment<TValue>, then the parameter builder's AddChildContent method should throw an exception with an error message telling the user to use .Add(p => p.ChildContent, ...) instead.

For example, the following should throw an helpful exception:

var cut = RenderComponent<Virtualize<string>>(ps => ps
	.Add(p => p.Items, Te

Using the table component is exceptionally good but the pagination is client side.

What would be nice is that we could use a table model to have pagination via server

It could be the exposing of a Total Records , Items per page properties and an event on the pagination buttons so we can "refill" the table.

I happen to be like you.
I wrote a Pagination component with 4 button,

Perhaps adding a CodeTour would help make it easier for new contributors to find their way around our project.

Let's look at using the CONTRIBUTING doc to make a snazzy CodeTour for future contributors to learn about our project

Currently we have a lot of public component props and methods but many of them should be private. We should revisit all components and make the necessary changes.

Here is an example from ErrorList component:
https://github.com/BlazorRepl/BlazorRepl/blob/5c7f061eb9cc75ac1121d70ba9f4828e9eb465c1/Client/Components/ErrorList.razor.cs#L22-L32

All of these properties and methods can be `privat