adding javalin-htmx examples to server integration examples #3104
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
Adding two examples of using htmx with the javalin server library
|
I'm not sure what strategy we use to order examples in that page, might be as simple as a "first come first served" so I can't tell you for sure about the order |
Telroshan
reviewed
Jan 9, 2025
Co-authored-by: Vincent <vichenzo-thebaud@hotmail.com>
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.
Adding two examples of using htmx and java with the javalin server library
Description
Adding two server-integration examples for java. Both of these examples use javalin and present a simpler approach to getting started with htmx and java than the current examples which use Spring Boot and Quarkus.
Corresponding issue:
#3099
Testing
I have reviewed a preview of my edits to this file.
Checklist
masterfor website changes,devforsource changes)
approved via an issue
npm run test) and verified that it succeeded