This repository has been archived by the owner on Jan 15, 2022. It is now read-only.
chore(deps): update dependency @vendure/core to v0.18.5 #135
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~0.17.0
->~0.17.0 || ~0.18.0
0.17.1
->0.18.5
Release Notes
vendure-ecommerce/vendure
v0.18.5
Compare Source
Fixes
Features
v0.18.4
Compare Source
Features
Fixes
v0.18.3
Compare Source
Fixes
Features
v0.18.2
Compare Source
Fixes
Features
v0.18.1
Compare Source
Fixes
Features
cancelJob
mutation (2d099cf), closes #614v0.18.0
Compare Source
Fixes
Features
amount
argument into createPayment method (0c85c76)BREAKING CHANGE
A change to the relation between OrderItems and Fulfillments means a database
migration will be required to preserve fulfillment data of existing Orders.
See the release blog post for details.
In order to support order modification, a couple of new default order states
have been created -
Modifying
andArrangingAdditionalPayment
. Also a new DB entity,OrderModification
has been created.The
OrderLine.pendingAdjustments
field has been renamed toadjustments
, taxadjustments are now stored in a new field,
taxLines
. This will require a DB migration topreserve data from existing Orders (see guide in release blog post)
The
PaymentMethodHandler.createPayment()
method now takes a newamount
argument. Update any custom PaymentMethodHandlers to use account for this new parameter and use
it instead of
order.total
when creating a new payment.The
TaxCalculationStrategy
has been renamed toProductVariantPriceCalculationStrategy
and moved in the VendureConfig fromtaxOptions
tocatalogOptions
and its API has been simplified.The
PriceCalculationStrategy
has been renamed toOrderItemPriceCalculationStrategy
.The Fulfillment and ShippingMethod entities have new fields relating to
FulfillmentHandlers. This will require a DB migration, though no custom data migration will be
needed for this particular change.
The
addFulfillmentToOrder
mutation input has changed: themethod
&trackingCode
fieldshave been replaced by a
handler
field which accepts a FulfillmentHandler code, and anyexpected arguments defined by that handler.
The ProductTranslation entity has had a constraint removed, requiring a schema
migration.
The return object of the ShippingCalculator class has changed:
This change will require you to update any custom ShippingCalculator implementations, and also
to update any ShippingMethods by removing and re-selecting the ShippingCalculator.
The Shop API mutations
setOrderShippingAddress
,setOrderBillingAddress
setOrderCustomFields
now return a union type which includes a newNoActiveOrderError
.Code which refers to these mutations will need to be updated to account for the union
with the fragment spread syntax
...on Order {...}
.The TaxCalculationStrategy return value has been simplified - it now only need
return the
price
andpriceIncludesTax
properties. TheProductVariant
entity has also beenrefactored to bring it into line with the corrected tax handling of the OrderItem entity. This
will require a DB migration. See release blog post for details.
The way shipping charges on Orders are represented has been changed - an Order
now contains multiple ShippingLine entities, each of which has a reference to a ShippingMethod.
This will require a database migration with manual queries to preserve existing order data. See
release blog post for details.
There have been some major changes to the way that Order taxes and discounts are handled. For a full discussion of the issues behind these changes see #573. These changes will
require a DB migration as well as possible custom scripts to port existing Orders to the new
format. See the release blog post for details.
The following GraphQL
Order
type properties have changed:subTotalBeforeTax
has been removed,subTotal
now excludes tax, andsubTotalWithTax
has been added.totalBeforeTax
has been removed,total
now excludes tax, andtotalWithTax
has been added.Configuration
📅 Schedule: "every weekend" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by WhiteSource Renovate. View repository job log here.