Rebuild Horizon's user interface with Inertia and React - #1807
Draft
nckrtl wants to merge 24 commits into
Draft
Conversation
Adjust package CI, ignore rules, and repository attributes for the Inertia rebuild without adding local AI contributor guidance.
Keep failed-job tag search draft text stable when poll responses arrive, and stop wrapping the whole dashboard in aria-live=polite.
Reuse DatabaseBatchCapability on the rewritten batches page so a missing job_batches table returns an empty list without report() noise.
Keep browser Inertia pages and legacy redirects on web routes with HandleInertiaRequests, and load JSON endpoints from routes/api.php under an api prefix without Laravel's stateless api middleware group.
Use StatisticLink for the batches-in-progress overview card so the whole card navigates to the batches page like the other overview stats.
Post-process generated route helpers with encodeURIComponent and rebase Horizon URLs without URL-constructor path normalization so backslashes survive for FQCNs while slash-containing queue/tag values remain valid.
PHPUnit only loads one class per *Test.php file by default; moving the custom path/proxy redirect cases into a matching filename ensures they run.
Extend UnitTest with a silent exception handler for report() paths so the Unit suite no longer boots Testbench or flushes Redis for this file.
Remove duplicated route-count, batch-capability, font-policy, and capability-mirror assertions; replace sleep-based mtime waits with backdated touch; and exercise 422 pause validation with capabilities forced on.
|
Thanks for submitting a PR! Note that draft PRs are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface. Pull requests that are abandoned in draft may be closed due to inactivity. |
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
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.
This PR is a response to the request to port my Horizon redesign into this project.
I prepared two approaches. The classic PR is the merge-oriented option for Horizon 5.x. It keeps Vue, Bootstrap, Sass, the existing API routes, and support for Laravel 9 through 13.
This future-oriented PR implements the same redesign with Inertia v3, React, Tailwind CSS, and shadcn. It provides the same Horizon functionality as the classic PR, but changes the frontend stack and raises the minimum supported Laravel and PHP versions. For that reason, it may be a better fit for Horizon 6.
There is a live demo based on my Horizon New Dawn concept. It uses the same stack, but also explores controls beyond this PR, including a queue detail page, terminating Horizon instances, and starting or stopping individual supervisors. Those controls would need separate agreement before becoming part of Horizon.
The new stack also makes it easier to support mobile layouts, which the live demo already demonstrates.
What this changes
/api/stats, and pause and throughput metadata to/api/workload. No existing response field is removed or renamed.