reactioncommerce / api-plugin-products

Products plugin for the Reaction API

This repository is deprecated

This code is now located in our monorepo here

api-plugin-products

Summary

Products plugin for the Reaction API

Developer Certificate of Origin

We use the Developer Certificate of Origin (DCO) in lieu of a Contributor License Agreement for all contributions to Reaction Commerce open source projects. We request that contributors agree to the terms of the DCO and indicate that agreement by signing all commits made to Reaction Commerce projects by adding a line with your name and email address to every Git commit message contributed:

Signed-off-by: Jane Doe <[email protected]>

You can sign your commit automatically with Git by using git commit -s if you have your user.name and user.email set as part of your Git configuration.

We ask that you use your real name (please no anonymous contributions or pseudonyms). By signing your commit you are certifying that you have the right have the right to submit it under the open source license used by that particular Reaction Commerce project. You must use your real name (no pseudonyms or anonymous contributions are allowed.)

We use the Probot DCO GitHub app to check for DCO signoffs of every commit.

If you forget to sign your commits, the DCO bot will remind you and give you detailed instructions for how to amend your commits to add a signature.

License

This Reaction plugin is GNU GPLv3 Licensed

api-plugin-products's Issues

Shops should be able to set global default for social sharing message

Currently the social sharing messages are generated for each product and there is not any way to set an app wide or shop-wide message for social sharing.

There should be a way to set default social sharing for the app or a shop via the social dashboard.

Add exact match search to metafields in products query

The products query performs a fuzzy search for metafieldKey and metafieldValue. While retaining this option to avoid behavioral changes of the API we would like to add the option to perform exact match search. A flag will be introduced as a query argument to switch between the two search options. The default search will be exact match and the user can set the flag to switch to fuzzy search.

Products query using metafields returns fuzzy matches

I'm using metafields on products to search for certain criteria - in this instance a SKU. I added metafields to some products using key: "SKU" value: "LSBP-U1Y-PD-TST" When I use the products query to search for these products the query also returns products with metavalues of "LSBP-U1Y-PD-TST1" and "LSBP-U1Y-PD-TST2".

Steps to Reproduce

The query is as follows:

query products ($shopId: ID!, $metakey: String!, $metavalue: String!) { 
    products (shopIds: [$shopId], metafieldKey: $metakey, metafieldValue: $metavalue) 
    { 
      nodes { 
        _id description title metafields {key value} 
        variants { _id title sku }
      }
    }
}

Variables:

{
    "shopId": "cmVhY3Rpb24vc2hvcDo3WVJKNmVveHRkYXRLZGVubQ==",
    "metakey": "SKU",
    "metavalue": "LSBP-U1Y-PD-TST"
}

Add peer dependency for tags plugin

Products uses the TagSortByField and TagConnection type in GraphQL, which lives in the tags plugin.

When work is done to move products over here, we need to be sure to install api-plugin-tags as a peerDependency.