@sveltia/cms 0.29.1 → 0.29.2

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
@@ -102,14 +102,16 @@ We are working hard to create a **significantly better alternative to Netlify CM
102
102
  - Uses the GraphQL API where possible for better performance, as mentioned above. You don’t need to set the `use_graphql` option to enable it for GitHub and GitLab.
103
103
  - 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 a hardcoded fallback to `master`[^27].
104
104
  - You can [disable automatic deployments](#disabling-automatic-deployments) by default or on demand to save costs and resources associated with CI/CD and to publish multiple changes at once[^24].
105
- - The GitLab backend support comes with background service status checking, just like GitHub.
105
+ - The GitLab backend support comes with background [service status](https://status.gitlab.com/) checking, just like GitHub. Checks are performed frequently and an incident notification is displayed prominently for both services.
106
106
  - You can quickly open the source file of an entry or asset in your repository using View on GitHub (or GitLab) under the 3-dot menu.
107
107
 
108
108
  ### Better i18n support
109
109
 
110
110
  - Sveltia CMS has been built with a multilingual architecture from the very beginning. You can expect top-notch i18n support, as it’s required by clients of maintainer [@kyoshino](https://github.com/kyoshino), who himself was a long-time Japanese localizer for Mozilla and currently lives in a [city](https://en.wikipedia.org/wiki/Toronto) where 150+ languages are spoken.
111
+ - Supports multiple files/folders i18n structure for file collections[^87]. To enable it, simply use the `{{locale}}` template tag in the `file` path option, e.g. `content/pages/about.{{locale}}.json` or `content/pages/{{locale}}/about.json`. For backward compatibility, the global `structure` option only applies to folder collections as before.
112
+ - Eliminates UI confusion — the Preview pane can be displayed without toggling i18n in the Content Editor.
111
113
  - You can easily switch between locales while editing with just a click on a button instead of a dropdown list.
112
- - Language labels appear in human-readable display names instead of ISO 639 language codes, which not everyone is familiar with. For example, it might be difficult to recognize `DE` as German or `NL` as Dutch.
114
+ - Language labels appear in human-readable display names instead of ISO 639 language codes, which not everyone is familiar with. (For example, it might be difficult to recognize `DE` as German, `NL` as Dutch, or `ZH` as Chinese.)
113
115
  - Fields in non-default locales are validated as expected[^13].
114
116
  - Boolean, DateTime, List and Number fields in the entry preview are displayed in a localized format.
115
117
  - [Integrates DeepL](#using-deepl-to-translate-entry-fields) to allow translation of text fields from another locale with one click.
@@ -123,7 +125,6 @@ We are working hard to create a **significantly better alternative to Netlify CM
123
125
  - Solves problems with Chinese, Japanese and Korean (CJK) [IME](https://en.wikipedia.org/wiki/Input_method) text input in the rich text editor for the Markdown widget[^54].
124
126
  - You can use the `{{locale}}` template tag in the [`preview_path`](https://decapcms.org/docs/configuration-options/#preview_path) collection option to provide site preview links for each language[^63].
125
127
  - You can [localize entry slugs](#localizing-entry-slugs) while linking the localized files[^80], thanks to the support for Hugo’s `translationKey`[^81].
126
- - Supports multiple files/folders i18n structure for file collections[^87]. To enable it, simply use the `{{locale}}` template tag in the `file` path option, e.g. `content/pages/about.{{locale}}.json` or `content/pages/{{locale}}/about.json`. The global `structure` option only applies to folder collections as before.
127
128
 
128
129
  ### Better collections
129
130
 
@@ -147,7 +148,7 @@ We are working hard to create a **significantly better alternative to Netlify CM
147
148
  - You can hide the preview of a specific field with `preview: false`.
148
149
  - Fields with validation errors are automatically expanded if they are part of nested, collapsed objects[^40].
149
150
  - When you click on a field in the Preview pane, the corresponding field in the Editor pane is highlighted. It will be automatically expanded if collapsed[^41].
150
- - The Preview pane displays the titles of all fields, making it easier to see which fields are filled in.
151
+ - The Preview pane displays all fields, including each title, making it easier to see which fields are populated.
151
152
  - Provides better scroll synchronization between the panes when editing or previewing an entry[^92].
152
153
  - You can use a full regular expression, including flags, for the widget `pattern` option[^82]. For example, if you want to allow 280 characters or less in a multiline text field, you could write `/^.{0,280}$/s` (but you can now use the `maxlength` option instead).
153
154
  - A long validation error message is displayed in full, without being hidden behind the field label[^59].
@@ -185,13 +186,14 @@ We are working hard to create a **significantly better alternative to Netlify CM
185
186
  - Relation
186
187
  - Field options are displayed with no additional API requests[^14]. The confusing `options_length` option, which defaults to 20, is therefore ignored[^76].
187
188
  - `slug` can be used for `value_field` to show all available options instead of just one in some situations[^91].
189
+ - Template strings with a wildcard like `{{cities.*.name}}` can also be used for `value_field`[^94].
188
190
  - `display_fields` is displayed in the Preview page instead of `value_field`.
189
191
  - The redundant `search_fields` option is not required in Sveltia CMS, as it defaults to `display_fields` (and `value_field`).
190
192
  - Select
191
193
  - It’s possible to select an option with value `0`[^56].
192
194
  - `label` is displayed in the Preview page instead of `value`.
193
195
  - String
194
- - When a YouTube video URL is entered in a String field, it appears as an embedded video in the preview pane.
196
+ - When a YouTube video URL is entered in a String field, it appears as an embedded video in the Preview pane.
195
197
  - Check your site’s [CSP](#setting-up-content-security-policy) if the preview doesn’t work.
196
198
  - When a regular URL is entered in a String field, it appears as a link that can be opened in a new browser tab.
197
199
  - Supports the `type` option that accepts `url` or `email` as a value, which will validate the value as a URL or email.
@@ -791,7 +793,7 @@ This software is provided “as is” without any express or implied warranty. W
791
793
  [^74]: Netlify/Decap CMS [#4209](https://github.com/decaporg/decap-cms/issues/4209)
792
794
  [^75]: Netlify/Decap CMS [#5472](https://github.com/decaporg/decap-cms/issues/5472)
793
795
  [^76]: Netlify/Decap CMS [#4738](https://github.com/decaporg/decap-cms/issues/4738)
794
- [^77]: Netlify/Decap CMS [#6565](https://github.com/decaporg/decap-cms/issues/6565)
796
+ [^77]: Netlify/Decap CMS [#3415](https://github.com/decaporg/decap-cms/issues/3415), [#6565](https://github.com/decaporg/decap-cms/issues/6565)
795
797
  [^78]: Netlify/Decap CMS [#2294](https://github.com/decaporg/decap-cms/issues/2294), [#3046](https://github.com/decaporg/decap-cms/issues/3046), [#4363](https://github.com/decaporg/decap-cms/issues/4363)
796
798
  [^79]: Netlify/Decap CMS [#5726](https://github.com/decaporg/decap-cms/issues/5726)
797
799
  [^80]: Netlify/Decap CMS [#5493](https://github.com/decaporg/decap-cms/issues/5493), [#6600](https://github.com/decaporg/decap-cms/issues/6600)
@@ -808,4 +810,5 @@ This software is provided “as is” without any express or implied warranty. W
808
810
  [^91]: Netlify/Decap CMS [#4954](https://github.com/decaporg/decap-cms/issues/4954)
809
811
  [^92]: Netlify/Decap CMS [#1466](https://github.com/decaporg/decap-cms/issues/1466)
810
812
  [^93]: Netlify/Decap CMS [#1000](https://github.com/decaporg/decap-cms/issues/1000)
813
+ [^94]: Netlify/Decap CMS [#5487](https://github.com/decaporg/decap-cms/issues/5487)
811
814
  [^100]: Netlify/Decap CMS [#5656](https://github.com/decaporg/decap-cms/issues/5656), [#5837](https://github.com/decaporg/decap-cms/issues/5837), [#5972](https://github.com/decaporg/decap-cms/issues/5972), [#6476](https://github.com/decaporg/decap-cms/issues/6476), [#6516](https://github.com/decaporg/decap-cms/issues/6516), [#6930](https://github.com/decaporg/decap-cms/issues/6930), [#6965](https://github.com/decaporg/decap-cms/issues/6965), [#7080](https://github.com/decaporg/decap-cms/issues/7080), [#7105](https://github.com/decaporg/decap-cms/issues/7105), [#7106](https://github.com/decaporg/decap-cms/issues/7106), [#7119](https://github.com/decaporg/decap-cms/issues/7119), [#7176](https://github.com/decaporg/decap-cms/issues/7176), [#7194](https://github.com/decaporg/decap-cms/issues/7194) — These `removeChild` crashes are common in React apps and seem to be caused by a [browser extension](https://github.com/facebook/react/issues/17256) or [Google Translate](https://github.com/facebook/react/issues/11538).