Skip to content
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

Remove offical support for Lumen #1425

Merged
merged 2 commits into from
Feb 20, 2023
Merged

Remove offical support for Lumen #1425

merged 2 commits into from
Feb 20, 2023

Conversation

mfn
Copy link
Collaborator

@mfn mfn commented Feb 19, 2023

Summary

I'm proposing to drop official support for Lumen for the following reasons:

  • Lumen itself is dead, per [1]

    Note: In the years since releasing Lumen, PHP has made a variety of wonderful performance improvements. For this reason, along with the availability of Laravel Octane, we no longer recommend that you begin new projects with Lumen. Instead, we recommend always beginning new projects with Laravel.

    Laravel Octact is just Laravel and no one using ide-helper with it needs anything special.

  • For now, the change is mostly on the logistics side (readme, run tests, issues). In the past we had some special code but over time this was already removed. For now people still can use it and nothing will break out of the blue, but eventually it might

There are a only a few Lumen related issues open currently which would be closed by this (#1105, #1069, #438). We would also reduce e-waste cycles on the integration test suite matrix.

[1] laravel/lumen@69b2657

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
    (note: for now only "on paper", not technically)
  • This change requires a documentation update
  • Misc. change (internal, infrastructure, maintenance, etc.)

Checklist

  • Existing tests have been adapted and/or new tests have been added
  • Add a CHANGELOG.md entry
  • Update the README.md
  • Code style has been fixed via composer fix-style

@mfn mfn self-assigned this Feb 19, 2023
@mfn
Copy link
Collaborator Author

mfn commented Feb 19, 2023

Note: static analysis test problem is unrelated and something else

I'm proposing to drop official suport for Lumen for the following reasons:
- Lumen itself is dead, per [1]
  > **Note:** In the years since releasing Lumen, PHP has made a variety of wonderful performance improvements. For this reason, along with the availability of [Laravel Octane](https://laravel.com/docs/octane), we no longer recommend that you begin new projects with Lumen. Instead, we recommend always beginning new projects with [Laravel](https://laravel.com).

  Laravel Octact is just Laravel and no one using ide-helper with it
  needs anything special.
- For now, the change is mostly on the logistics side (readme, run tests,
  issues). In the past we had some special code but over time this was
  already removed.
  For now people still can use it and nothing will break out of the blue,
  but eventually it might

There are a only a few Lumen related issues open currently which would
be closed by this (barryvdh#1105, barryvdh#1069, barryvdh#438).

[1] laravel/lumen@69b2657
@mfn
Copy link
Collaborator Author

mfn commented Feb 19, 2023

@barryvdh WDYT?

@mfn mfn requested a review from barryvdh February 19, 2023 19:40
@barryvdh
Copy link
Owner

barryvdh commented Feb 20, 2023

I guess we could, but do we actually make any changes for Lumen? It's still about 5% of the downloads of Laravel itself.
image

I would suggest we drop it if we actually run into problems.

@mfn
Copy link
Collaborator Author

mfn commented Feb 20, 2023

I would suggest we drop it if we actually run into problems.

That's the thing, people have reported various issues over time because the integration is not straight forward and requires hacks/workarounds.

We currently have no in-code hacks (AFAIK) but also it doesn't work out of the box.

No matter the graphs, they don't correlate with laravel-ide-helper anyway.

We don't PREVENT them to make it work, but I think it's time to make a stance and acknowledge:

  • Lumen is on its way out
  • therefore laravel-ide-helper also does not provide active support/fixes

Technically, except merging the PR, we won't do anything.

We will not prevent it from working. But if we make a change in the spirit Laravel and it breaks Lumen (even more), we make it clear we don't support it.

Does that make (more) sense? 🤔

@barryvdh barryvdh merged commit 4dc20b0 into barryvdh:master Feb 20, 2023
@barryvdh
Copy link
Owner

Yeah I guess

@mfn mfn deleted the mfn-rm-lumen branch February 20, 2023 13:47
@mfn mfn mentioned this pull request Jan 28, 2024
9 tasks
d3v2a pushed a commit to d3v2a/laravel-ide-helper that referenced this pull request Feb 16, 2024
I'm proposing to drop official suport for Lumen for the following reasons:
- Lumen itself is dead, per [1]
  > **Note:** In the years since releasing Lumen, PHP has made a variety of wonderful performance improvements. For this reason, along with the availability of [Laravel Octane](https://laravel.com/docs/octane), we no longer recommend that you begin new projects with Lumen. Instead, we recommend always beginning new projects with [Laravel](https://laravel.com).

  Laravel Octact is just Laravel and no one using ide-helper with it
  needs anything special.
- For now, the change is mostly on the logistics side (readme, run tests,
  issues). In the past we had some special code but over time this was
  already removed.
  For now people still can use it and nothing will break out of the blue,
  but eventually it might

There are a only a few Lumen related issues open currently which would
be closed by this (barryvdh#1105, barryvdh#1069, barryvdh#438).

[1] laravel/lumen@69b2657

Co-authored-by: Barry vd. Heuvel <barry@fruitcake.nl>
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.

None yet

2 participants