[Blazor] Unfortunate parameter naming

[javiercn]

RegisterForJavaScript contains a parameter named "javaScriptInitializer". This is unfortunate because it conflicts with the name of a feature "JS initializers" in an area where both are applicable, and it is being the source of confusion for customers.

Customers are confused because they don't know if the "initializer" refers to a JS initializer file, or to something else.

We should consider renaming the parameter: At least give it a different name to avoid running into this situation, something like componentFunctionSetup or something like that.

You can read the details #37074

[SQL-MisterMagoo]

It is definitely unfortunate naming that led me down the wrong route (I had to step through the client side code to see why it wasn't working)

If the same/similar functionality can be made to work in the "JS initializers" feature (it doesn't currently) then removing the parameter from this API would definitely get my vote.

[Swimburger]

I like having the API available, but agree it could be confusing name-wise. It's a good name, but overlapping with that other feature mentioned.

[SteveSandersonMS]

After discussion we decided not to change this. The feature isn't as much of a name clash as it first seemed, since root component initializers serve a specific purpose independent of package JS initializers.

[SQL-MisterMagoo]

Will there at least be some documentation to clarify how "javaScriptInitilizer" is configured in your project to use it?

At the moment, searching the docs for javaScriptInitializer finds no results : https://docs.microsoft.com/en-us/search/?scope=ASP.NET%20Core&view=aspnetcore-6.0&terms=javaScriptInitializer