Add full GQL support to product editor

[mikemurray]

Resolves #168 #184 #212 #216 #220 #223
Impact: major
Type: feature|refactor

Issue

There are many issues with the current meteor specific implementation of the product admin.

Solution

• Fix all of those problems and convert it to GraphQL
• Removed the template field (it's not available in the API in 3.0)
• Removed the google plus message field from the social for.

Breaking changes

none.

Testing

1. Use api with this PR: feat: Fixes for product editor reaction#6141
2. Use the admin and make sure everything works in the product editor

(non-critical issues can go into a list and I can address them in another PR.)

[mikemurray]

@willopez Ok... This is enough for this PR. The editor still needs some work, especially to the media gallery block, but for the most part, everything is in place and seems to work. I'd like to push any non-critical feedback into a fresh PR.

One issue, in particular, would be with the Media Gallery editor. I've put those issues into this ticket: #236

[janus-reith]

@mikemurray When changes are saved and the updated Product is returned, publishedProductHash and currentProductHash are the same, so the Publish button won't become active.

After a page reload the changes are visible, ot by doing a second change in order to get a new refetch. That state would be old again:
I could take a published Product with Title "ABC 123", change it to "ABC 1234", Publish button greyed out. Then change it back to "ABC 123", and the Publish button becomes active.

Might need api changes to correctly deliver a new hash directly upon change, or else, an artifical delay like for images.
Update: I just figured out that simply adding another refetchProduct inside onUpdateProduct does the trick for now without another artifical delay here.
However, that still is not a clean solution, as the Payload of updateProduct is expected to have all the fresh Product data, therefore not requiering a manual refetch.

[janus-reith]

The TagSelector Component needs overflow-y: visible in order to display a List of Tags properly, else it would be cut of at the Dialog height.
The issue is noticable when having 3 or more Tags to choose from.

As this is broken in the catalyst library, one option is to define a custom theme override in the admin's theme:
MuiDialog: { paper: { overflowY: "visible" } }

Certainly better to fix this in catalyst.

[mikemurray]

@janus-reith
Product hash: Yea, I've seen that happen sometimes. We probably need to look at the API to see why the hash isn't delivered with the result on time. It might be doing the has async with an app event or something.

MUI Dialog: I agree, probably best to fix the default in Catalyst.

[mikemurray]

@janus-reith Just checked, and yes, the hasProduct function runs on an the app events afterProductUpdate and afterVariantUpdate. So just like the media, we're going to have to figure out a solution to this async stuff.

[willopez]

I am adding non-critical issues to another issue here: #237. Other than those issues noted in #237 this is a good foundation to build on.

[willopez]

Approving so that we can merge this and start fixing issues on new PRs. The issues found are in issue #237.