Skip to content

Support of graphqlite 7 and symfony 7 #70

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

Merged
merged 6 commits into from
Apr 13, 2024

Conversation

fogrye
Copy link
Contributor

@fogrye fogrye commented Mar 28, 2024

As symfony 7 completely drops support of doctrine annotations I think it's a great timing to drop them and fix this project to work with attributes.

{
if (! isset($values['for'])) {
throw new BadMethodCallException('The @Assert annotation must be passed a target. For instance: "@Assert(for="$email", constraint=@Email)"');
/**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a breaking change, no ? I mean people upgrading might get errors if they are using Annotations.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes that's BC to support symfony 7

@nguyenk
Copy link
Member

nguyenk commented Mar 29, 2024

Hello @fogrye , thanks a mile for your PR. I'm afraid we might have a breaking change while supporting both version 6 and 7 and introducing attributes. If someone using version 6 with Annotations, they will get errors using src/Annotations/Assertion.php as an Annotation.

What do you think ?

BC: annotation support dropped, use attributes
@fogrye
Copy link
Contributor Author

fogrye commented Mar 29, 2024

@nguyenk doctrine annotations are deprecated for a long time and were finally removed in symfony v7, technically somebody can have an issue in symfony 6 with attributes but we have to make it that way

@fogrye fogrye requested a review from nguyenk April 1, 2024 06:43
@SCIF
Copy link

SCIF commented Apr 1, 2024

@nguyenk , attributes is the way. rector can help with migration. Why not just release v7.0 of the bridge and drop symfony v6 support?

@fogrye
Copy link
Contributor Author

fogrye commented Apr 1, 2024

drop symfony v6 support

Symfony v6 is in LTS, I would not drop that.

@SCIF
Copy link

SCIF commented Apr 1, 2024

drop symfony v6 support

Symfony v6 is in LTS, I would not drop that.

I mean to drop the support of symfony v6 in bridge v7. But bridge v6 can still be maintained/supported.

@fogrye
Copy link
Contributor Author

fogrye commented Apr 2, 2024

@nguyenk so I prepared PR to be pushed as v7 because of BC.

@fogrye
Copy link
Contributor Author

fogrye commented Apr 8, 2024

Hi @nguyenk I'm also participating in removal of annotations support for graphqlite so I think it's completely ok to drop them in this project. Waiting patiently for your approval.

@fogrye
Copy link
Contributor Author

fogrye commented Apr 13, 2024

@nguyenk I see you're not so active lately, I can help you with maintenance of this lib so it would not become a blocker for graphqlite-bundle

@nguyenk nguyenk merged commit 2f677f6 into thecodingmachine:master Apr 13, 2024
@nguyenk
Copy link
Member

nguyenk commented Apr 13, 2024

Hello folks ! Thank you both for you contribution @SCIF and @fogrye. I'm currently off, and was previously very busy. I did see your proposal to contribute more actively. Let's discuss this further next time I become a blocker again :).

v7.0 has just been released.

@fogrye I guess you would like to continue with this one ? thecodingmachine/graphqlite-bundle#203

Cheers

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.

3 participants