Add Datastar request generation from Endpoint definitions #3750
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.
Summary
This PR adds support for generating Datastar fetch expressions directly from ZIO HTTP
Endpoint
definitions. Instead of manually writing Datastar request strings, developers can now automatically generate them from their endpoint definitions.Motivation
When using Datastar with ZIO HTTP endpoints, developers had to manually construct Datastar fetch expressions like
@get('/api/users')
. This was error-prone and didn't leverage the type-safe endpoint definitions we already have. This PR bridges that gap.Changes
Core Implementation
EndpointRequest
- New trait representing a Datastar request action with method, URL, headers, and optionsEndpointRequestBuilder
- Builder class for constructing requests from endpoints with fluent APItoDatastarRequest
toEndpoint
for easy conversiondataFetch
shortcuts inAttributes
trait for quick request creationFeatures
Testing
data-on
attributesDocumentation
Usage Example
Checklist
Related Issues
Closes #3697
/claim #3697