Will PageScript be absorbed directly into the Blazor framework? #15
Description
Hi Mackinnon,
This PageScript mechanism enabled me to create a server-side site with static and interactive rendering. My router, main layout and home landing page are all statically rendered. The idea being, everything is static by default, and save the interactivity and signalr for only pages/components that absolutely require it.
Without PageScript, this project would have been more complex, especially with enhanced navigation enabled.
That said, is there any move to incorporate this as part of the Blazor framework?
My concern is if I start using this paradigm for sites in general where I work, I become dependent upon PageScript being available and kept up to date!
I might be wrong, but it looks like this required someone with your internal knowledge of Blazor to develop, or at least much easier for someone with that inside knowledge compared to the public.
So, please let us know if this is up for consideration into Blazor, as having a method for page-specific JS that plays nice with Enhanced Navigation seems like an absolute necessity, and perhaps a tech debt from the .NET 8 release.
Thank you and great work!
-Brian