Feature/Product type

[kidunot89]

Your checklist for this pull request

Thanks for sending a pull request! Please make sure you click the link above to view the contribution guidelines, then fill out the blanks below.

🚨Please review the guidelines for contributing to this repository.

• Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• Make sure you are requesting to pull request from a topic/feature/bugfix branch (right side). Don't pull request from your master!

What does this implement/fix? Explain your changes.

Tests

• ProductQueriesTest

Enum Types

• BackorderEnum
• CatalogVisibilityEnum
• DiscountType
• StockStatus
• TaxStatus

Object Types

• Product
• ProductAttribute

Connections

• Coupon<->Products - products, excludedProducts
• Coupon<->ProductCategories - productCategories, excludedProductCategories
• Product<-> Products - upsell, crossSell, variations
• Product<->ProductCategories - categories
• Product<->ProductTags - tags
• Product<->ProductAttribute - attributes, defaultAttributes
• Product<->MediaItem - galleryImages

Query example

query {
    product(id: \"{$product->get_id()}\") {
        productId
        name
        slug
        date
        modified
        status
        featured
        catalogVisibility
        description
        shortDescription
        sku
        price
        regularPrice
        salePrice
        dateOnSaleFrom
        dateOnSaleTo
        totalSales
        taxStatus
        taxClass
        manageStock
        stockQuantity
        stockStatus
        backorders
        soldIndividually
        weight
        length
        width
        height
        reviewsAllowed
        purchaseNote
        menuOrder
        virtual
        downloadable
        shippingClassId
        downloads
        downloadLimit
        downloadExpiry
        ratingCount
        averageRating
        reviewCount
        upsell {
            nodes {
                ...Product fields
            }
        }
        crossSell {
            nodes {
                ...Product fields
            }
        }
        parent {
            ...Product fields
        }
        categories {
            nodes {
                ...Taxonomy fields
            }
        }
        tags {
            nodes {
                ...Taxonomy fields
            }
        }
        image {
            ...MediaItem fields
        }
        galleryImages {
            nodes {
                ...MediaItem fields

            }
        }
        attributes {
            nodes {
               id
               name
               position
               visible
               variation
               options
            }
        }
        defaultAttributes {
            nodes {
               id
               name
            }
        }
    }
}

Does this close any currently open issues?

…

Any relevant logs, error output, GraphiQL screenshots, etc?

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Any other comments?

…

Where has this been tested?

Operating System: Ubuntu 18.04

WordPress Version: 5.1

[renatonascalves]

A few questions! Looking good! :)

[renatonascalves]

@kidunot89 Is the idea to create a product implementation for each type of products? WC_Product_Simple, WC_Product_Variation, etc?

If yes, can we do something to verify the WC_Product and classes that extend WC_Abstract_Legacy_Product?

That would allow WC_Product_Subscription_Variation, WC_Product_Subscription, and other product types to work without having to create their own product implementation.

[kidunot89]

resolve_product is only used in the root queries product and productBy, however I will add the ability to filter the resolver of the Product type, if this does not work for other Woo extensions

[renatonascalves]

There should be WC_Product_Simple and others here as well.

[kidunot89]

I'm waiting for the Model Layer PR to be completed before optimizing base on queried fields. That way optimization can be done in Product model and I can avoid having to refactor.