Open
Conversation
…t`, `request_animation_frame`, and `request_idle_callback` (#4388)
…d from `leptos_axum` (#4309)
… `.into_reactive_value()` on both nightly and stable (#4523)
…4536) * feat: Allow customizing the status code of server fn error responses Currently, all server function error responses have status code 500. This is not ideal, especially when it comes to observability. If every error response has status 500, then it's difficult to see which errors are client errors (404, unauthorized access attempts, etc) vs which ones are actual internal server errors that need to be investigated. This PR builds on #4249 to allow customizing the http status code for server function error responses. * Convert between two different versions of `http::status::StatusCode`
…, unifying API with `ShowLet` and `AnimatedShow` (#4466)
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
8 participants
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.
Over time, a number of small changes have piled up that are semver-breaking but don't affect user code in significant ways. I'm opening a "Leptos 0.9" PR and
leptos_0.9branch now for visibility. I don't anticipate significant migration needed for any of these, although publishing a new version always does create some ecosystem churn as dependencies need to update as well.