Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contributing back a few things I've learned along the way using Blazor Static SSR with HTMX.
I added a middleware to check whether we are in an HTMX request. Since this project has some server interactivity, I felt that was safer than trying to use IHttpContextAccessor.
App.razorandMainLayout.razornow short-circuit to avoid a complete render during HTMX requests. This allowsLoveHtmx.razorto be routable rather than needing an API call.I've found that the syntax of writing minimal APIs gets a bit clunky, particularly when capturing form data. I added an example of using a Controller with a RazorComonentResult, which I am affectionately dubbing "Model-Blazor-Controller".
This results in demonstrating four ways to call the LoveHtmx component:
I also bumped HTMX to 2.0 while listening to the upgrade music