This repository has been archived by the owner on Jan 15, 2022. It is now read-only.
chore(deps): update dependency @vendure/testing to v0.18.5 #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/vendure-testing-0.x
branch
from
d128ef0
to
6466f38
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/vendure-testing-0.x
branch
from
6466f38
to
3e30e54
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/vendure-testing-0.x
branch
from
3e30e54
to
1d64940
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/vendure-testing-0.x
branch
from
1d64940
to
4858d95
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/vendure-testing-0.x
branch
from
4858d95
to
783d77f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/vendure-testing-0.x
branch
from
783d77f
to
c589b49
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/vendure-testing-0.x
branch
from
c589b49
to
9998205
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/vendure-testing-0.x
branch
from
9998205
to
bf32a38
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/vendure-testing-0.x
branch
from
bf32a38
to
2395136
Compare
renovate
bot
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.16.1->0.18.5Release Notes
vendure-ecommerce/vendure
v0.18.5Compare Source
Fixes
Features
v0.18.4Compare Source
Features
Fixes
v0.18.3Compare Source
Fixes
Features
v0.18.2Compare Source
Fixes
Features
v0.18.1Compare Source
Fixes
Features
cancelJobmutation (2d099cf), closes #614v0.18.0Compare Source
Fixes
Features
amountargument 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 -
ModifyingandArrangingAdditionalPayment. Also a new DB entity,OrderModificationhas been created.The
OrderLine.pendingAdjustmentsfield 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 newamountargument. Update any custom PaymentMethodHandlers to use account for this new parameter and use
it instead of
order.totalwhen creating a new payment.The
TaxCalculationStrategyhas been renamed toProductVariantPriceCalculationStrategyand moved in the VendureConfig fromtaxOptionstocatalogOptionsand its API has been simplified.The
PriceCalculationStrategyhas 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
addFulfillmentToOrdermutation input has changed: themethod&trackingCodefieldshave been replaced by a
handlerfield 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,setOrderBillingAddresssetOrderCustomFieldsnow 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
priceandpriceIncludesTaxproperties. TheProductVariantentity 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
Ordertype properties have changed:subTotalBeforeTaxhas been removed,subTotalnow excludes tax, andsubTotalWithTaxhas been added.totalBeforeTaxhas been removed,totalnow excludes tax, andtotalWithTaxhas been added.v0.17.3Compare Source
This release fixes an error in publishing the last release. No changes have been made.
v0.17.2Compare Source
Features
Fixes
v0.17.1Compare Source
Features
activeAdministratorquery to Admin API (70e14f2)updateActiveAdministratormutation (73ab736)Fixes
v0.17.0Compare Source
Fixes
Features
shouldRunCheckfunction to ShippingEligibilityChecker (3b7e7db), closes #536instring filter for PaginatedList queries (7c7dcf2), closes #543regexstring filter for PaginatedList queries (0a33441), closes #543Perf
BREAKING CHANGE
Deletions of Orders or Customers now cascade to any associated HistoryEntries,
thus preserving referential integrity. This involves a DB schema change which will necessitate
a migration.
Fulfillments now start in the new "Created" state, and then immediately
transition to the "Pending" state. This allows e.g. event listeners to pick up newly-created
Fulfillments.
Orders now start in the new "Created" state, and then immediately transition
to the "AddingItems" state. This allows e.g. event listeners to pick up newly-created Orders.
The
AuthenticationStrategy.onLogOut()functionsignature has changed: the first argument is now the RequestContext of the current request.
The
OrderItem.unitPriceis now always given as the net (without tax) priceof the related ProductVariant. Formerly, it was either the net or gross price, depending on
the
pricesIncludeTaxsetting of the Channel. If you have existing Orders whereunitPriceIncludesTax = true, you will need to manually update theunitPricevalue beforerunning any other migrations for this release. The query will look like:
UPDATE order_item SET unitPrice = ROUND(unitPrice / ((taxRate + 100) / 100)) WHERE unitPriceIncludesTax = 1The
OrderLine.totalPricefield has been deprecated and will be removed in afuture release. Use the new
OrderLine.linePriceWithTaxfield instead.The
PaymentMethodHandlerfunction signatures have changed:createPayment(),settlePayment()&createRefund()now all get passed theRequestContext object as the first argument.
The
PriceCalculationStrategy.calculateUnitPrice()functionsignature has changed: the first argument is now the RequestContext of the current request.
The
ProductVariant.trackInventoryfield is now an Enum rather than a boolean, allowing explicit inheritance of the value set in GlobalSettings. This will require a DB migration with a custom query to transform the previous boolean values to the new enum (string) values of "TRUE", "FALSE" or "INHERIT". Check the release blog post for more details.The
ShippingMethodentity is now translatable. This change will require a DBmigration to be performed, including custom queries to migrate any existing ShippingMethods
to the new table structure (see release blog post for details).
The AssetNamingStrategy
generateSourceFileName()&generatePreviewFileName()function signatures have changed: the first argument is now the
RequestContext of the current request.
The AssetPreviewStrategy
generatePreviewImage()function signature has changed: the first argument is now the
RequestContext of the current request.
The internal handling of stock movements has been refined,
which required changes to the DB schema. This will require a migration.
The OrderMergeStrategy
merge()function signature has changed: the first argument is now the
RequestContext of the current request.
The PromotionAction
execute()function signature has changed: the first argument is now the
RequestContext of the current request.
The ShippingCalculator
calculate()function signature has changed: the first argument is now the
RequestContext of the current request.
The ShippingEligibilityChecker
check()function signature has changed: the first argument is now the
RequestContext of the current request.
The TaxZoneStrategy
determineTaxZone()function signature has changed: the first argument is now the
RequestContext of the current request.
v0.16.3Compare Source
Fixes
Features
v0.16.2Compare Source
Fixes
loadData()function after filters run (e22db7e), closes #518Features
Configuration
📅 Schedule: "every month" (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 this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.