goravel-crud-routes

To register CRUD API routes for a Goravel entity, you provide the entity name to automatically inject endpoints like Index, Show, Store, Update, and Delete into routes/api.go. This eliminates repetitive boilerplate and ensures consistent endpoint wiring.

Setting up admin web routes for Goravel entities involves automatically adding Inertia-based page routes under admin paths in routes/web.go. This aligns with entity route conventions and separates optional public endpoints from protected operations.

Goravel requires specific route ordering, placing search endpoints before {id} parameters to prevent routing conflicts. Following this constraint ensures proper endpoint matching and adheres to hyphenated plural route naming conventions across API and web layers.

You can separate public and auth-protected routes in Goravel by distinguishing optional public endpoints from protected operations during route generation. This applies across both API and web route files, ensuring proper access control layers.

To stop writing repetitive routing boilerplate for new Goravel entities, you automate the routing setup by injecting all necessary API and web routes. Supplying the entity name wires all CRUD operations and admin UI paths immediately.