Skip to content

Inertia.js v2.0 compatibility #671

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 122 commits into
base: 1.x
Choose a base branch
from
Draft

Inertia.js v2.0 compatibility #671

wants to merge 122 commits into from

Conversation

reinink
Copy link
Member

@reinink reinink commented Oct 9, 2024

This PR prepares the Inertia Laravel adapter for Inertia.js v2.0.

Additionally, it also drops support for Laravel 8 and 9, as well as PHP 7.x and 8.0.

Note: this PR won't actually ever get merged, as we're going to have both a 1.x and 2.x branch moving forward.

joetannenbaum and others added 30 commits April 10, 2025 10:53
[2.x] Resolve Closure before checking if a prop implements the Arrayable contract
Handle SSR URLs with trailing slashes
[2.x] Call `toArray()` on `Arrayable` props resolved from the Container
…aracters

  This PR provides a more consistent approach to URL handling in Inertia responses by:

  - Adding support for preserving trailing slashes in URLs
  - Improving readability by decoding special characters in query parameters
  - Maintaining compatibility with proxy prefixes
  - Ensuring URL consistency for SEO and debugging

  Previously, characters like slashes (%2F) and ampersands (%26) were encoded in the URL,
  making debugging more difficult and causing inconsistencies between browser URLs and
  Inertia history state URLs.

  Comprehensive tests have been added for both trailing and non-trailing slash scenarios,
  as well as specific tests for slash and ampersand handling in query parameters.

  Resolves issues discussed in #663
Improve URL handling with support for trailing slashes
[2.x] Introduce inertiaProps Method in TestResponseMacros for Improved Inertia.js Testing
[2.x] Remove check for `TestResponse` from Laravel <= 6.0
[2.x] Check Vite manifest before Mix manifest
[2.x] Allow deepMerge on custom properties
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.