Split package: Htmxor.Declarations (or Htmxor.Abstractions) and Htmxor

egil / Htmxor

Supercharges Blazor static server side rendering (SSR) by seamlessly integrating the Htmx.org frontend library.

MIT License

102 stars 12 forks source link

Split package: Htmxor.Declarations (or Htmxor.Abstractions) and Htmxor #61

Open megafetis opened 1 week ago

megafetis commented 1 week ago

Is it possible to split package to two: Htmxor.Declarations (or Htmxor.Abstractions) and Htmxor ? To use some attributes, interfaces in webassembly side without including serverside features

egil commented 1 week ago

I'm not opposed to it, but can you share more details about the use case?

megafetis commented 1 week ago

Thank @egil ! Example: Solution, where:

aspnet core project as render server
wasm host project
blazor projects as parts of web app where may be ht-* markup and direct routing pages.
some scenarios involve only rendering and further use of htmx (not wasm)
some scenarios involve rendering and further launch wasm host. When runs aspnet core host, it registers routing for htmx. But when the wasm host is launched, most of the code intended for the server gets into the client part.

egil commented 1 week ago

Sorry, I still not follow exactly what you are trying to do. Can you elaborate?

megafetis commented 1 week ago

I just trying to reduce size of wasm payload. Now problem is solving by IL trimming. So problem is not critical. In future splitting packages would be an elegant solution.