Release 3.23.30 [automated] - #6877
Closed
saleor-deployments[bot] wants to merge 1 commit into
Closed
Conversation
Contributor
Differences Found✅ No packages or licenses were added. SummaryExpand
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 3.23 #6877 +/- ##
=======================================
Coverage 56.78% 56.78%
=======================================
Files 3542 3542
Lines 73488 73488
Branches 19034 19030 -4
=======================================
Hits 41728 41728
Misses 29813 29813
Partials 1947 1947
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or 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
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.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to 3.23, this PR will be updated.
Releases
saleor-dashboard@3.23.30
Patch Changes
#6876
ce6966fThanks @mirekm! - You can now filter customers by attributes.On the customer list, open Conditions and choose Attribute.
#6867
e258774Thanks @mirekm! - Customer types are now in the Customers sidebar.Open Customers to jump to All, or to a type such as B2B or Default. Customer Types at the bottom opens the type settings. If you only have one type, the menu stays All plus settings — that type is the same list as All. Types you pin on the customer list appear first; only a handful of types are listed so the menu stays short.
#6876
ce6966fThanks @mirekm! - Improve filter menus so they show more choices and load on scroll.#6655
7002c5aThanks @lkostrowski! - Fixed the product page freezing while it loads. The media card re-rendereditself in a loop until the product query resolved, which could lock up the tab
on slower connections.
#6875
070d0e6Thanks @lkostrowski! - Removed the gift card code export from the Dashboard: the "Export card codes" menu item on thegift card list and the export dialog are gone. The feature is deprecated —
exportGiftCardsisremoved from the 3.24 API, and on 3.23 it can still be used directly via the API.
Bulk issuing gift cards no longer opens a follow-up dialog offering to email the codes — the
success notification is now the only confirmation, since exporting was that dialog's only action.
#6655
7002c5aThanks @lkostrowski! - Rich text fields (product, category and collection descriptions, CMS pages, andrich text attributes) now support images. Pick "Image" from the editor toolbar
and paste a link to an externally hosted image, or paste the link straight into
the editor.
Uploading files to Saleor media storage is not supported yet, so dragging,
dropping or pasting an image file does nothing.
Note: storefronts and other API clients that render rich text content need to
handle the
imageblock to display these images.#6873
e2fe430Thanks @ebrahim2355! - Lists no longer crash when rows stay selected while the list shrinks.Selecting rows and then lowering "rows per page", bulk-deleting, or refetching fewer records could take the whole view down with "We've encountered an unexpected error". Glide tracks its row selection by index, independently of the data, so the grid reported indices that no longer pointed at a row and the list resolved them straight onto its own data. Products, collections, models, draft orders, shipping zones and gift cards were affected. Attribute and voucher lists did not crash but could put undefined entries into the selection that bulk actions run on.
#6871
bc08ccfThanks @lkostrowski! - Fixed every attribute request failing against the 3.24 API. The Dashboard kept selectingavailableInGrid,filterableInStorefrontandstorefrontSearchPosition, which 3.24 removesfrom
Attribute, so attribute list, details and update all returned validation errors.Those three fields are now marked as belonging to the 3.23 schema only and are dropped from the
request when the Dashboard is built against 3.24. On 3.23 the storefront faceted navigation
settings keep working unchanged. Sorting the attribute list by "Use in faceted search" falls back
to sorting by name on 3.24, where that sort field is gone too.