Release 1.15.0 #4549
Merged
Release 1.15.0 #4549
Conversation
…rrowed from storefront)
…reaction into feat-dan-graphql-customer-grid-experiment
…b.com/reactioncommerce/reaction into feat-dan-graphql-customer-grid-experiment
…reaction into feat-4353-dancastellon-sitemap-generator
…reaction into feat-4353-dancastellon-sitemap-generator
…reaction into feat-4353-dancastellon-sitemap-generator
…reaction into feat-4353-dancastellon-sitemap-generator
…reaction into feat-dan-graphql-customer-grid-experiment
…onenumber-js #4516: Move formatPhoneNumber (and libphonenumber-js) server-side to reduce client bundle
…-sitemap-generator #4353 Plugin for auto-generated sitemaps
…t-improvements Fulfillment improvements
…ion rather than Meteor method
…tEmailOnAnonymousCart GraphQL: Replace "cart/setAnonymousUserEmail" Meteor method with setEmailOnAnonymousCart mutation
…regate-order feat: improve orders sub speed by rearranging pipeline
… into release-1.15.0
… get the context in removeFromCart method
…art-remove-item (fix): remove last item from anon cart
Detailed Sheet: |
5c58334
into
master
11 of 12 checks passed
11 of 12 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
v1.15.0
Sitemap Generator
A sitemap generator plugin that creates and stores XML for a sitemap index, as well as sitemaps for tag pages, PDPs, and arbitrary URLs that can be added via an event hook.
There is a recurring job that runs every 24 hours (the specific interval can be changed) that generates the sitemaps. There is also a button to manually trigger a refresh, at Dashboard -> Shop -> Options - along with a notification that appears when it's completed.
Use our GraphQL API for the Product Grid within the Meteor App
As part of our push towards our GraphQL API, we've started to leverage the API inside of our existing Meteor app. This release converts our customer facing product grid from using Meteor Pub/Sub to consuming data from our GraphQL API instead. This is the first step in an ongoing initiative to start using the GraphQL API inside of our existing monolithic commerce application. See #4481 for a list of files changed.
GraphQL Checkout
This release includes the first set of GraphQL APIs designed for stepping through a checkout. While we've started to consume this API within our Storefront Starter Kit, these APIs should be treated as unstable and subject to change. We've added mutations for setting an anonymous email -
setEmailOnAnonymousCart
and selecting fulfillment options -selectFulfillmentOptionForGroup
.A note on fulfillment options
Fulfillment options are what we're calling what used to be shipment options. In order to prepare ourselves for several types of fulfillment that do not necessarily include shipping, we're updating the checkout through order models, methods, and now our GraphQL API to be capable of grouping items into "Fulfillment Groups". This opens the door for several new types of fulfillments down the line such as In Store Pickup, Digital Downloads, Digital Key Generation, and anything else you can think up. We're not actively building any of these different fulfillment types into core, but want to ensure that it's possible and there's a clear direction to do so.
Breaking Changes
Shipment
schema to remove theitems
property. This will cause a breaking change for plugins expecting the items property to be there. Such plugins should be updated to use a combination of itemIds and the main items list. (#4531)requiresShipping
prop from products and catalog products. This has been replaced by an arraysupportedFulfillmentTypes
. Reaction's core admin interface did not provide a method for setting this prop, and we've left thesupportedFulfillmentTypes
out of the exiting operator interface. This change will emable us to show a "Shipping"/"Pick Up" selector for other items down the road. Will also permit creation of digital fulfillment types, etc. (#4554)cart/setAnonymousUserEmail
Meteor method is removed. This does not break any core behavior, but it might require updates to any custom plugins.GraphQL DevServer
Features
Fixes
Meteor App
Features
Performance
Fixes
Refactor
Chores
Contributors