@sveltia/cms 0.10.0 → 0.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -49,7 +49,9 @@ Here are some highlights mainly compared to Netlify/Decap CMS:
49
49
 
50
50
  ### Better productivity
51
51
 
52
- - You can [work on a local Git repository](#work-with-a-local-git-repository) without having to run a proxy server on your machine.
52
+ - You can [work on a local Git repository](#work-with-a-local-git-repository) without having to run a proxy server on your machine[^26].
53
+ - The Git branch name is automatically set to the repository’s default branch (`main`, `master` or whatever) if not specified in the configuration file, preventing data loading errors due to fallback to `master`[^27].
54
+ - Never miss out on the latest features and bug fixes by being notified when an update to the CMS is available[^31].
53
55
  - You can delete multiple entries and assets at once.
54
56
  - Some keyboard shortcuts are available for faster editing. More to come!
55
57
  - Create a new entry: `Ctrl+E` (Windows/Linux) / `Command+E` (macOS)
@@ -71,7 +73,10 @@ Here are some highlights mainly compared to Netlify/Decap CMS:
71
73
  - Fields in non-default locales are validated as expected[^13].
72
74
  - [Integrates DeepL](#use-deepl-to-translate-entry-fields) to allow translation of text fields from another locale with one click.
73
75
  - You can [disable non-default locale content](#disable-non-default-locale-content)[^15].
74
- - You can [use a random UUID for an entry slug](#use-a-random-id-for-an-entry-slug), which is a good option for locales that write in non-Latin characters[^12].
76
+ - You can [use a random UUID for an entry slug](#use-a-random-id-for-an-entry-slug), which is a good option for locales that write in non-Latin characters. Sveltia CMS also supports the proposed `uuid` widget with the following properties[^12]:
77
+ - `prefix`: A string to be prepended to the value. Default: an empty string.
78
+ - `use_b32_encoding`: Whether to encode the value with Base32. Default: `false`.
79
+ - `read_only`: Whether to make the field read-only. Default: `true`.
75
80
  - Resolves the [limitations in the list and object widgets](https://decapcms.org/docs/i18n/#limitations) so that changes made with these widgets will be duplicated between locales as expected when using the `i18n: duplicate` field configuration[^7].
76
81
  - [Entry-relative media folders](https://decapcms.org/docs/collection-folder/#media-and-public-folder) can be used in conjunction with the `multiple_folders` i18n structure[^21].
77
82
 
@@ -80,10 +85,12 @@ Here are some highlights mainly compared to Netlify/Decap CMS:
80
85
  - You can choose a [custom icon for each collection](#use-a-custom-icon-for-a-collection)[^3].
81
86
  - A [per-collection media folder](#use-a-custom-media-folder-for-a-collection) will appear next to the entries.
82
87
  - String values in YAML files can be quoted with the new `yaml_quote: true` option for a collection, mainly for framework compatibility[^9].
88
+ - Entry slug template tags support [filter transformations](https://decapcms.org/docs/summary-strings/) just like summary string template tags[^29].
83
89
  - You can set the maximum number of characters for an entry slug with the new `slug_length` collection option[^25].
84
90
 
85
91
  ### Better fields/widgets
86
92
 
93
+ - The Boolean, Number and String widgets support the `prefix` and `suffix` properties, allowing developers to display custom messages before and/or after the field[^28].
87
94
  - Relation field options are displayed with no additional API requests[^14]. The `options_length` property is therefore ignored.
88
95
  - Required fields, not optional fields, are clearly marked for efficient data entry.
89
96
  - Provides a reimagined all-in-one asset selection dialog for file and image fields.
@@ -91,6 +98,7 @@ Here are some highlights mainly compared to Netlify/Decap CMS:
91
98
  - New assets can be uploaded by dragging & dropping them into the dialog[^20].
92
99
  - A file/image URL can also be entered in the dialog.
93
100
  - Integration with Pexels, Pixabay and Unsplash makes it easy to select and insert free stock photos[^8].
101
+ - The Object widget supports [variable types](https://decapcms.org/docs/variable-type-widgets/) just like the List widget. This allows you to have dependent fields in a collection[^30].
94
102
  - Optional object fields (`widget: object` with `required: false`) can be manually added or removed. If unadded or removed, the required subfields won’t trigger validation errors[^16].
95
103
  - You can revert changes to all fields or a specific field.
96
104
 
@@ -439,4 +447,10 @@ This software is provided “as is” without any express or implied warranty. W
439
447
  [^22]: [Netlify/Decap CMS #6642](https://github.com/decaporg/decap-cms/issues/6642)
440
448
  [^23]: [Netlify/Decap CMS #2](https://github.com/decaporg/decap-cms/issues/2)
441
449
  [^24]: [Netlify/Decap CMS #6831](https://github.com/decaporg/decap-cms/issues/6831)
442
- [^25]: [Netlify/Decap CMS #6987](https://github.com/decaporg/decap-cms/issues/6987)
450
+ [^25]: [Netlify/Decap CMS #526](https://github.com/decaporg/decap-cms/issues/526), [#6987](https://github.com/decaporg/decap-cms/issues/6987)
451
+ [^26]: [Netlify/Decap CMS #3285](https://github.com/decaporg/decap-cms/issues/3285)
452
+ [^27]: [Netlify/Decap CMS #3285](https://github.com/decaporg/decap-cms/issues/5617)
453
+ [^28]: [Netlify/Decap CMS #6836](https://github.com/decaporg/decap-cms/pull/6836)
454
+ [^29]: [Netlify/Decap CMS #4783](https://github.com/decaporg/decap-cms/pull/4783)
455
+ [^30]: [Netlify/Decap CMS #565](https://github.com/decaporg/decap-cms/pull/565)
456
+ [^31]: [Netlify/Decap CMS #1045](https://github.com/decaporg/decap-cms/pull/1045)