OpenAPITools / OpenAPITools/openapi-generator

[REQ] Laravel generator status

Open
#20,437 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement: Feature Server: PHP
Dominant language
Java
Stars
26.8k
Forks
7.7k
PR merge metrics
PR metrics pending

Description

Is your feature request related to a problem? Please describe.

I’ve been looking into the Laravel generator and noticed it could use some love. It's outdated and doesn’t fully align with the OpenAPI generator philosophy. It also doesn’t reflect some of the modern approaches seen in other generators, like the Symfony generator. This makes it harder to use the generated code without significant customization.

Describe the solution you'd like

First, I’d like to understand the current status of the Laravel generator:

  • Is it actively maintained?
  • If so, who is the current maintainer?

If there’s no active maintainer, I’d like to help improve it. My goal would be to rewrite parts of the Laravel generator to make it more user-friendly. For example, I really like how the Symfony generator produces a complete controller and leaves the API interface for the user to implement—it’s clean and efficient. I think the Laravel generator could benefit from a similar approach.

I’d also update it to support the latest PHP and Laravel versions (like PHP 8.3 and Laravel 11) and ensure it’s ready for modern development. Beyond that, I’d explore other improvements, but those are my initial ideas.

Additional context

I think improving the Laravel generator could save a lot of time for developers and make it much easier to integrate with modern projects. I’d love to hear more about its current status and whether anyone’s actively maintaining it. If not, I’d be happy to contribute and help bring it up to speed!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named. Start by reviewing the Laravel generator and comparing it with the Symfony generator; confirm its maintenance status and supported PHP and Laravel versions, then define a concrete, agreed scope before implementation can be considered done.

Written by the indexing model from the issue text.

Assessment

Tech stack
laravel, php
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.