-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
[RFC]: Remove laminas-db from require-dev #107
Comments
Kill it with 🔥 as @Ocramius would say We dropped the record not|exists validators in v3 of validator. This stuff belongs in its own package and users can always copy/paste the implementation from older releases if neccesary. |
Even if I think this is right, it always raises questions.
This path should be taken. |
I'd say "drop it", and we then move it to a separate package, as @froschdesign correctly mentions. The dependency graph needs to be slimmed down here |
@laminas/technical-steering-committee |
@arhimede
Maybe a project will help here or an issue report with sub-issues. |
Ok, I created few sub-issues, the last one worries me 😄 |
https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues |
@froschdesign i moved all those subissues under the main issue , #101 |
RFC
Goal
Remove laminas-db from require-dev and remove the SaveHandler DbTableGateway class
Background
Currently, in composer , at the require-dev section, it's called the
laminas-db
package.Also, composer allow PHP 8.4 but
laminas-db
does not allow it (yet).laminas-db
is in security mode, so we should not use it in new releasesConsiderations
We should decide if the save handler TableGateway is a MUST
If we should remove it or replace it with something else....
Proposal(s)
Remove laminas-db from require-dev and remove the SaveHandler DbTableGateway class
The text was updated successfully, but these errors were encountered: