Hey, I’m developing a new tap for Shopify that uses their GraphQL API and supports bulk endpoints. I decided to make it because other taps use REST, which is being deprecated and missing some new fields. I also used it to test creating dynamic discovery logic for GraphQL. It’s a bit hacky, but it works. Let me know if you have any feedback or requests for the tap. I’ll push it to the Hub next week if there are no major issues. https://github.com/sehnem/tap-shopify

The Matatika variant is well maintained and I’m sure they’d be interested in updating it to use GraphQL. Have you looked at contributing to that variant? https://github.com/Matatika/tap-shopify cc @aaron_phethean @daniel_walker @Reuben (Matatika) 😄

great! I will take a look at it, as the schemas are different we will need to discuss how to integrate them, but I would gladly add my changes to it

Would gladly accept a PR for this. 😊

@Reuben (Matatika) the graphql schemas are pretty different from the REST ones, do you think that creating new streams for the graphql ones would be an issue or do you have an other suggestion?

A similar discussion with @pat_nadolny came up recently around updating tap-google-analytics to support ga4. The approached we used for tap-gitlab was to create a new branch. That would let users that have a

pip_url

pointing to the current main branch to not experience breaking changes.

@edgar_ramirez_mondragon that is a good point, I will search about how Shopify intend to support the REST version, I know that new fields are not being added, maybe they have plans to shut it down in the future as it was the case with GA3, so a branch would make sense, while the Graphql version of the tap gets stable. Also it would avoid fragmentation.