Allow turbo streams for unprocessable entity responses#56
Merged
marcelolx merged 1 commit intorails:mainfrom Mar 20, 2023
Merged
Conversation
Since Rails can respond with 422 when form validation fails for example, allow request.js to perform and render turbo stream messages for both 200 and 422 response codes.
marcelolx
approved these changes
Mar 20, 2023
Member
|
I just hit the same issue. @marcelolx Is there any chance to have it released in the stable version? |
Collaborator
|
@morgoth I will see if I can push a release tomorrow morning! |
Collaborator
Member
|
Thank you |
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
3 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.
Since Rails can respond with 422 when form validation fails for example, allow request.js to perform and render turbo stream messages for both 200 and 422 response codes.