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

Release 2024-01 #1011

Merged
merged 3 commits into from Feb 5, 2024
Merged

Release 2024-01 #1011

merged 3 commits into from Feb 5, 2024

Conversation

nozzlegear
Copy link
Owner

Releasing 7.0 is going to take a little longer than I thought, so I’m going to push out 2024-01 as part of 6.13.0.

I realize this contains breaking changes for the generated GraphQL types, but I think I’m okay with that. Since ShopifySharp doesn’t version itself the same way Shopify versions their API, it’s bound to happen and I don’t want to release a new major version each time they deprecate or change their graph (or rest) types.

@nozzlegear nozzlegear added this to the 6.13.0 milestone Feb 5, 2024
@nozzlegear nozzlegear merged commit 0ab4b5a into master Feb 5, 2024
@nozzlegear nozzlegear deleted the 2024-01 branch February 5, 2024 07:06
@clement911
Copy link
Collaborator

I personally think it's ok to increment the major version regularly.
As an example, I use Stripe quite a bit, and they are already at major version 43!

Here we could increment to 7. And when you do your other changes, we could increment to 8, even if it's shortly after...

@nozzlegear
Copy link
Owner Author

nozzlegear commented Feb 5, 2024 via email

@clement911
Copy link
Collaborator

Yes I believe they follow semver like most libraries. So each major increment is a breaking change.
But it doesn't mean that it's hard to upgrade. Just that there is at least one breaking change.

@adearriba
Copy link
Contributor

QQ: How are you guys generating the graphql types?

@clement911
Copy link
Collaborator

At a high level, the code generation of graphql type uses a graphql introspection query to load all types and generate some c# code.
It can be triggered by running the test in (after removing the Skip attribute) https://github.com/nozzlegear/ShopifySharp/blob/master/ShopifySharp.Tests/GenerateGraphQLSchema_Test.cs

@adearriba
Copy link
Contributor

Thanks @clement911 I was asking more on which code generator you guys were using for this.

@nozzlegear
Copy link
Owner Author

We're using a generator that Clement wrote called Wish.GraphQLSchemaGenerator. He explained it here in #962!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants