Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
Repo to demonstrate the Issue: https://github.com/MariovanZeist/BlazorInferenceCallback
Although my use case is for Table and Grid like components I will demonstrate the feature using a simpler component:
Assume this component: (A generic list component with a click event that has the clicked item as a parameter)
InferAndCallback.razorWe will supply the component with a List of
Ingredient, and (optionally) supply a click event to handle selecting the ingredient.index.razorDescribe the solution you'd like
I would prefer to not have to specify the
Ttype parameter directly, and instead, let it be inferred by the generated code.so
Would compile without specifying the TypeParam
Additional context
This is probably due to how the source is generated:
I cleaned the generated source up a bit to show the difference, and the problem:
this is the relevant part of the generated source file: with comments to show the problem:
{ [Microsoft.AspNetCore.Components.RouteAttribute("/")] public partial class Index : Microsoft.AspNetCore.Components.ComponentBase { #pragma warning disable 1998 protected override void BuildRenderTree(Microsoft.AspNetCore.Components.Rendering.RenderTreeBuilder __builder) { //<InferAndCallBack Items=Ingredient.Ingredients /> __Blazor.BlazorInferenceCallback.Pages.Index.TypeInference.CreateInferAndCallBack_0(__builder, 0, 1, Ingredient.Ingredients); //^ This compiles to and works correctly //<InferAndCallBack Items=Ingredient.Ingredients SelectEvent=SelectedIngredient /> __Blazor.BlazorInferenceCallback.Pages.Index.TypeInference.CreateInferAndCallBack_1(__builder, 3, 4, Ingredient.Ingredients, 5, Microsoft.AspNetCore.Components.EventCallback.Factory.Create(this, SelectedIngredient)); //^This fails because it generates an EventCallback instead of an EventCallback<T> // and the CreateInferAndCallBack_1 function expects an EventCallback<T> //It should be: //__Blazor.BlazorInferenceCallback.Pages.Index.TypeInference.CreateInferAndCallBack_1(__builder, 3, 4, Ingredient.Ingredients, 5, Microsoft.AspNetCore.Components.EventCallback.Factory.Create<Ingredient>(this, SelectedIngredient)); //<InferAndCallBack T=Ingredient Items=Ingredient.Ingredients SelectEvent=SelectedIngredient/> __builder.OpenComponent<BlazorInferenceCallback.Components.InferAndCallBack<Ingredient>>(7); __builder.AddAttribute(8, "Items", global::Microsoft.AspNetCore.Components.CompilerServices.RuntimeHelpers.TypeCheck<System.Collections.Generic.IEnumerable<Ingredient>>(Ingredient.Ingredients)); __builder.AddAttribute(9, "SelectEvent", global::Microsoft.AspNetCore.Components.CompilerServices.RuntimeHelpers.TypeCheck<Microsoft.AspNetCore.Components.EventCallback<Ingredient>>(Microsoft.AspNetCore.Components.EventCallback.Factory.Create<Ingredient>(this, SelectedIngredient))); __builder.CloseComponent(); //^As we specified the type, no type inference is needed so we can generate the code as any other non generic component } } } namespace __Blazor.BlazorInferenceCallback.Pages.Index { #line hidden internal static class TypeInference { public static void CreateInferAndCallBack_0<T>(global::Microsoft.AspNetCore.Components.Rendering.RenderTreeBuilder __builder, int seq, int __seq0, global::System.Collections.Generic.IEnumerable<T> __arg0) { __builder.OpenComponent<global::BlazorInferenceCallback.Components.InferAndCallBack<T>>(seq); __builder.AddAttribute(__seq0, "Items", __arg0); __builder.CloseComponent(); } public static void CreateInferAndCallBack_1<T>(global::Microsoft.AspNetCore.Components.Rendering.RenderTreeBuilder __builder, int seq, int __seq0, global::System.Collections.Generic.IEnumerable<T> __arg0, int __seq1, global::Microsoft.AspNetCore.Components.EventCallback<T> __arg1) { __builder.OpenComponent<global::BlazorInferenceCallback.Components.InferAndCallBack<T>>(seq); __builder.AddAttribute(__seq0, "Items", __arg0); __builder.AddAttribute(__seq1, "SelectEvent", __arg1); __builder.CloseComponent(); } } }The text was updated successfully, but these errors were encountered: