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
Developers can apply versioning without staging (i.e. just version history, no draft/live) by applying the extension using the .versioned-suffixed service name, e.g.:
This naming doesn’t really explain what this variant of the extension does. The full versioning mode is suffixed .stagedversioned, which I suspect is where the .versioned suffix came from, but as the default alias for Versioned::class points to .stageversioned, no one ever uses or sees the suffix.
Suggest we adjust the non-staged suffix better explain what this mode is, possible alternatives:
Versioned::class . '.versioningonly'
Versioned::class . '.nostages'
Versioned::class . '.historyonly'
Naming things is always hard, open to suggestions 😄
We can keep the existing service name as an alias, either temporarily to make the CMS5 upgrade slightly easier or just keep it forever (it’s a single line in YAML)
The text was updated successfully, but these errors were encountered:
Developers can apply versioning without staging (i.e. just version history, no draft/live) by applying the extension using the
.versioned
-suffixed service name, e.g.:This naming doesn’t really explain what this variant of the extension does. The full versioning mode is suffixed
.stagedversioned
, which I suspect is where the.versioned
suffix came from, but as the default alias forVersioned::class
points to.stageversioned
, no one ever uses or sees the suffix.Suggest we adjust the non-staged suffix better explain what this mode is, possible alternatives:
Versioned::class . '.versioningonly'
Versioned::class . '.nostages'
Versioned::class . '.historyonly'
Naming things is always hard, open to suggestions 😄
We can keep the existing service name as an alias, either temporarily to make the CMS5 upgrade slightly easier or just keep it forever (it’s a single line in YAML)
The text was updated successfully, but these errors were encountered: