You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to strongly structure certain areas of my website and assign the translationKey uniformly. e.g. the translationKey of my blog posts should be pre-assigned with post-. This value prefix should not be editable.
Unfortunately, I got this idea from the existing prefix / suffix implementation, but there is a different functionality here.
The text was updated successfully, but these errors were encountered:
Well yes, I’ve implemented decaporg/decap-cms#6836 a few weeks ago, but I think prefix and suffix for the UI visibility purpose are ill-named. Another PR decaporg/decap-cms#6675 I have also implemented uses prefix in the right way.
I think no one uses it in Sveltia CMS yet; I could rename the current prefix/suffix properties to something else, say before_input/after_input, and implement this as prefix/suffix.
I think no one uses it in Sveltia CMS yet; I could rename the current prefix/suffix properties to something else, say before_input/after_input, and implement this as prefix/suffix.
I would like to strongly structure certain areas of my website and assign the
translationKey
uniformly. e.g. thetranslationKey
of my blog posts should be pre-assigned withpost-
. This value prefix should not be editable.Unfortunately, I got this idea from the existing
prefix
/suffix
implementation, but there is a different functionality here.The text was updated successfully, but these errors were encountered: