So after wasting the best part of a year getting my head around the sheer over complexities of shopify GraphQL I would like to ask someone, anyone at shopify who actually knows anything.
WHY
Why release a graphql command to then superceed it only months later, instead of fixing it you simply just realise newer commands (sorry nodes and edges), the AI DEV you have is useless its constantly giving the wrong information - try it - it still says use input - thats now been removed so you now need to use productid instead.
Have you ever heared the expression, if its not broke dont fix it ?
We all knew where we stood with REST API, it either worked or didnt.
Coding that I wrote back in June / July 2024, I came to add into our system in November 2024 only to find you had deprecaited the commands already - and i had to do the work all over agian, come on.
Its not suprising I am actively suggesting woocommerce and others to people, how can we say in good faith when you keep moving the goal posts ?
Only this week, I found the new productUpdate overwrites TAGS, so unless you pass them over during an update, Shopify either deletes them, replaces them with Tags1, Tags2, or even something else.
Do you guys not test this stuff out ?
This is what your so called AI wizard came up with
------------
Shopify's behavior to update the tags field when you use the productUpdate mutation depends on how the tags are handled in the input. If you do not explicitly provide a tags field in the input, Shopify may interpret it as an instruction to clear the existing tags.
In your query, no tags field is included in the input. Here's what happens:
Implicit Clearing:
When you update a product without specifying the tags field, Shopify might assume you intend to remove all existing tags. This behavior can vary based on the Shopify API version you are using.
Default Behavior:
Some Shopify API versions or configurations default to overwriting tags when the tags field is omitted. This means existing tags are cleared because no tags are explicitly provided.
Workaround:
To ensure tags remain unchanged, explicitly include the current tags in the input. For example:
--------------------
That is just fantastic guys, correct me if i am wrong, the whole selling point was graphql was so cool as you only updated just the bits you want, well now i cant i've got to include the tags everytime
I wonder how many other people have noticed that the TAGS simply are deleted, changed without consent ?
I can imagine the sheer frustration of people who use automation in their searches on pages that look at the tags.
Can anyone, please anyone, pray tell - provide a proper time frame, a proper this is our plan for the next 12-18 months - rather than this hit and miss approach, oh that doesnt work lets just create another node, another edge, another another and another, you only have to look at the release of the ProductBulkUpdate as the previous attempt failed.
I would truely be embarrsed to say i worked at shopify as a developer.
