sanity-plugin-media
6.5.06.6.0
~
Modified (4 files)
File too large for inline diff
Index: package/package.json
===================================================================
--- package/package.json
+++ package/package.json
@@ -1,7 +1,7 @@
{
"name": "sanity-plugin-media",
- "version": "6.5.0",
+ "version": "6.6.0",
"description": "This version of `sanity-plugin-media` is for Sanity Studio V3.",
"keywords": [
"asset",
"browser", File too large for inline diff
Index: package/README.md
===================================================================
--- package/README.md
+++ package/README.md
@@ -225,8 +225,11 @@
When `locales` are provided, all localized fields (title, altText, description, creditLine) are grouped by language in tabs. Each tab shows all fields for a single language, making it easy to edit translations for many languages in a compact interface.
This will return the Italian value if present, otherwise English, otherwise French, etc. Adjust the order as needed for your project.
+**Sorting by title:**
+When `locales` are configured, "Title: A to Z" / "Title: Z to A" in the sort dropdown sort by the first available translation, checked in the order your `locales` array is declared — the same fallback pattern shown above. Assets missing a title in every configured locale sort as empty.
+
#### Migrating existing assets to localized format
If you enable `locales` on a project that already has assets with plain string fields (e.g. `title: "My photo"`), you should run the provided migration script to convert those fields to the localized object format (e.g. `title: {en: "My photo"}`).