@sveltia/cms 0.76.1 → 0.77.1
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 +9 -3
- package/dist/sveltia-cms.js +236 -238
- package/dist/sveltia-cms.js.map +1 -1
- package/dist/sveltia-cms.mjs +232 -234
- package/dist/sveltia-cms.mjs.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -128,7 +128,7 @@ While we fix reported bugs as quickly as possible, usually within 24 hours, our
|
|
|
128
128
|
- Ensuring substantial [compatibility with Netlify/Decap CMS](#compatibility)
|
|
129
129
|
- Providing partial [compatibility with Static CMS](#compatibility-with-static-cms)
|
|
130
130
|
- Tackling as many [Netlify/Decap CMS issues](https://github.com/decaporg/decap-cms/issues) as possible
|
|
131
|
-
- So far,
|
|
131
|
+
- So far, 210+ issues, or 420+ if including duplicates, have been effectively solved in Sveltia CMS
|
|
132
132
|
- Target:
|
|
133
133
|
- 200 issues, or 400 if including duplicates, by GA (we did it!)
|
|
134
134
|
- 350 issues, or 700 if including duplicates, in the future
|
|
@@ -140,7 +140,7 @@ While we fix reported bugs as quickly as possible, usually within 24 hours, our
|
|
|
140
140
|
- Responding to requests from the maintainer’s clients
|
|
141
141
|
- Making the code clean and maintainable
|
|
142
142
|
|
|
143
|
-
<br>
|
|
144
144
|
|
|
145
145
|
## Differentiators
|
|
146
146
|
|
|
@@ -300,6 +300,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
300
300
|
- The `date` transformation supports the time zone argument. The only available value is `utc`, which converts a date to UTC. This is useful if the specified DateTime field is local, but you want to force UTC in the entry slug, e.g. `{{date | date('YYYYMMDD-HHmm', 'utc')}}`. ([Discussion](https://github.com/sveltia/sveltia-cms/issues/278#issuecomment-2565313420))
|
|
301
301
|
- The `date` transformation returns an empty string if an invalid date is given.[^176]
|
|
302
302
|
- Multiple transformations can be chained like `{{title | upper | truncate(20)}}`.
|
|
303
|
+
- The collection `label` defaults to the `name` value according to the [Decap CMS document](https://decapcms.org/docs/configuration-options/#collections), while Netlify/Decap CMS actually throws a configuration error if the `label` option is omitted.
|
|
303
304
|
- Nested fields (dot notation) can be used in the `path` option for a folder collection, e.g. `{{fields.state.name}}/{{slug}}`.[^62]
|
|
304
305
|
- Markdown is supported in the `description` collection option.[^79] Bold, italic, strikethrough, code and links are allowed.
|
|
305
306
|
- The collection `folder` can be an empty string (or `.` or `/`) if you want to store entries in the root folder. This supports a typical VitePress setup.
|
|
@@ -403,7 +404,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
403
404
|
- 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.
|
|
404
405
|
- An optional List field with no subfield or value is saved as an empty array, rather than nothing.[^44]
|
|
405
406
|
- An optional List field won’t populate an item by default when the subfield has the `default` value.[^162]
|
|
406
|
-
-
|
|
407
|
+
- A simple list field with no subfields is displayed as a multiline text field,[^219] where users can use spaces[^50] and commas[^220] for list items. A comma is no longer treated as a list delimiter.
|
|
407
408
|
- Users can preview variable types without having to register a preview template.[^42]
|
|
408
409
|
- 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.
|
|
409
410
|
- A collapsed List field will not display a programmatic summary like `List [ Map { "key": "value" } ]` if the `summary` option is not set.[^183]
|
|
@@ -433,6 +434,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
433
434
|
- The redundant `search_fields` option is optional in Sveltia CMS, as it defaults to `display_fields`, `value_field` or the collection’s `identifier_field`, which is `title` by default.
|
|
434
435
|
- The `value_field` option is also optional in Sveltia CMS, as it defaults to entry slugs (`{{slug}}`).
|
|
435
436
|
- A new item created in a referenced collection is immediately available in the options.[^138]
|
|
437
|
+
- It’s possible to refer to a list field with the `field` option, which produces a single subfield but does not output the subfield `name` in the data, using the `value_field: cities.*.name` syntax. ([Discussion](https://github.com/sveltia/sveltia-cms/discussions/400))
|
|
436
438
|
- Select
|
|
437
439
|
- It’s possible to select an option with value `0`.[^56]
|
|
438
440
|
- `label` is displayed in the Preview Pane instead of `value`.
|
|
@@ -1781,3 +1783,7 @@ This software is provided “as is” without any express or implied warranty. W
|
|
|
1781
1783
|
[^217]: Netlify/Decap CMS [#5467](https://github.com/decaporg/decap-cms/issues/5467)
|
|
1782
1784
|
|
|
1783
1785
|
[^218]: Netlify/Decap CMS [#978](https://github.com/decaporg/decap-cms/issues/978)
|
|
1786
|
+
|
|
1787
|
+
[^219]: Netlify/Decap CMS [#3018](https://github.com/decaporg/decap-cms/issues/3018)
|
|
1788
|
+
|
|
1789
|
+
[^220]: Netlify/Decap CMS [#2153](https://github.com/decaporg/decap-cms/issues/2153)
|