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
{{ message }}
This repository was archived by the owner on Sep 16, 2025. It is now read-only.
fix(slugification): do not update slug once generated (#68)
Attempting to update the slug on updates was causing issues with `slugifyWithCount` increasing the number when it should not. Once a slug is generated it should never be auto updated as it can cause unintended side effects.
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,6 +71,7 @@ Per [#35](https://github.com/ComfortablyCoding/strapi-plugin-slugify/issues/35)
71
71
| contentTypes[modelName]field | The name of the field to add the slug | String | N/A | Yes |
72
72
| contentTypes[modelName]references | The name(s) of the field(s) used to build the slug. If an array of fields is set it will result in a compound slug | String or Array | N/A | Yes |
73
73
| slugifyWithCount | Duplicate strings will have their occurrence appended to the end of the slug | Boolean | false | No |
74
+
| shouldUpdateSlug | Allow the slug to be updated after initial generation. | Boolean | false | No |
74
75
| skipUndefinedReferences | Skip reference fields that have no data. Mostly applicable to compound slug | Boolean | false | No |
75
76
| slugifyOptions | The options to pass the the slugify function. All options can be found in the [slugify docs](https://github.com/sindresorhus/slugify#api)| Object | {} | No |
0 commit comments