@sveltia/cms 0.58.4 → 0.59.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 +8 -1
- package/dist/sveltia-cms.js +186 -186
- package/dist/sveltia-cms.js.map +1 -1
- package/dist/sveltia-cms.mjs +181 -181
- package/dist/sveltia-cms.mjs.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -285,6 +285,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
285
285
|
- The maximum number of characters for an entry slug can be set with the new `slug_length` collection option to avoid deployment errors with Netlify or other platforms.[^25]
|
|
286
286
|
- Setting the collection `path` doesn’t affect the entry slugs stored with the Relation widget.[^137]
|
|
287
287
|
- Entry slugs are [localizable](#localizing-entry-slugs).[^80]
|
|
288
|
+
- Users can edit entry slugs via the 3-dot menu in the Content Editor.[^184]
|
|
288
289
|
- Entry listing
|
|
289
290
|
- [Default sort field and direction](#specifying-default-entry-sort-field-and-direction) can be specified.[^172]
|
|
290
291
|
- Sorting entries by a DateTime field works as expected.[^110]
|
|
@@ -365,12 +366,13 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
365
366
|
- The `min` and `max` options can be used separately. You don’t need to specify both to use either option.[^145]
|
|
366
367
|
- The Add Item button appears at the bottom of the list when the `add_to_top` option is not `true`, so you don’t have to scroll up each time to add new items.
|
|
367
368
|
- Users can expand or collapse the entire list, while the Expand All and Collapse All buttons allow you to expand or collapse all items in the list at once.[^164]
|
|
368
|
-
- A required List field with no subfield or value is marked as invalid.[^43]
|
|
369
|
+
- A required List field with no subfield or value is marked as invalid.[^43] No need to set the `min` and `max` options for the `required` option to work.
|
|
369
370
|
- An optional List field with no subfield or value is saved as an empty array, rather than nothing.[^44]
|
|
370
371
|
- An optional List field won’t populate an item by default when the subfield has the `default` value.[^162]
|
|
371
372
|
- Users can enter spaces in a simple text-based List field.[^50]
|
|
372
373
|
- Users can preview variable types without having to register a preview template.[^42]
|
|
373
374
|
- It’s possible to omit `fields` in a variable type object.[^163] In that case, only the `typeKey` (default: `type`) is saved in the output.
|
|
375
|
+
- A collapsed List field will not display a programmatic summary like `List [ Map { "key": "value" } ]` if the `summary` option is not set.[^183]
|
|
374
376
|
- Markdown
|
|
375
377
|
- The rich text editor is built with the well-maintained [Lexical](https://lexical.dev/) framework, which solves various issues with a [Slate](https://github.com/ianstormtaylor/slate)-based editor in Netlify/Decap CMS, including fatal application crashes,[^71][^72][^73][^111] lost formatting when pasting,[^124] an extra line break when pasting,[^169] backslash injections,[^53] dropdown visibility,[^70] and text input difficulties with IME.[^54]
|
|
376
378
|
- The default editor mode can be set by changing the order of the `modes` option.[^58] If you want to use the plain text editor by default, add `modes: [raw, rich_text]` to the field configuration.
|
|
@@ -490,6 +492,7 @@ However, 100% feature parity is not planned, and some features are still missing
|
|
|
490
492
|
- The theme and keymap inline settings of the Code widget will not be supported, and some languages are dropped, as we use the [Prism](https://prismjs.com/)-powered code block functionality in Lexical instead of [CodeMirror](https://codemirror.net/).
|
|
491
493
|
- Remark plugins will not be supported, as they are not compatible with our Lexical-based rich text editor.
|
|
492
494
|
- [Undocumented methods](https://github.com/sveltia/sveltia-cms/blob/c69446da7bb0bab7405be741c0f92850c5dddfa8/src/main.js#L14-L37) exposed on the `window.CMS` object will not be implemented. This includes custom backends and custom media libraries, if any. We may support these features in the future, but our implementation would likely be incompatible with Netlify/Decap CMS.
|
|
495
|
+
- An absolute URL for the [`public_folder`](https://decapcms.org/docs/configuration-options/#public-folder) option will not be supported, as such configuration is not recommended, as stated in the Netlify/Decap CMS document.
|
|
493
496
|
|
|
494
497
|
### Features to be implemented before GA
|
|
495
498
|
|
|
@@ -1483,3 +1486,7 @@ This software is provided “as is” without any express or implied warranty. W
|
|
|
1483
1486
|
[^181]: Netlify/Decap CMS [#6254](https://github.com/decaporg/decap-cms/issues/6254)
|
|
1484
1487
|
|
|
1485
1488
|
[^182]: Netlify/Decap CMS [#4416](https://github.com/decaporg/decap-cms/issues/4416)
|
|
1489
|
+
|
|
1490
|
+
[^183]: Netlify/Decap CMS [#1275](https://github.com/decaporg/decap-cms/issues/1275)
|
|
1491
|
+
|
|
1492
|
+
[^184]: Netlify/Decap CMS [#377](https://github.com/decaporg/decap-cms/issues/377)
|