[0.5.x] [BREAKING] Require Precognition-Success
header
#41
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.
🚨 Breaking change. Requires a major version bump, i.e.,
0.5.x
.We introduced a new header to determine if Precognition was truly successful.
To ease migration and not impact existing applications using Precognition that had not yet updated to v10.11.0 (2023-05-16), I intentionally delayed adding it to our JS package.
With the introduction of the testing helpers, I felt this was a good time to make this breaking change and bring everything inline.
This is now a required header for responses, meaning that when this new version is tagged - consuming Laravel applications will need to update to
^10.11.0
.For applications that have not yet updated to
^10.11.0
, you may put the following in yourbootstrap.js
orapp.js
to maintain the previous functionality until you can update your Laravel framework version.VueJS + Inertia
VueJS
React + Inertia
React