Add option to automatically generate slug from another field #258
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ellmetha
reviewed
Aug 13, 2024
ellmetha
reviewed
Aug 31, 2024
treagod
force-pushed
the
slugify-field-option
branch
2 times, most recently
from
ac1427b
to
0c99d3e
Compare
treagod
force-pushed
the
slugify-field-option
branch
from
0c99d3e
to
f2600b6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this change a slug field accepts a
slugifyparameter, which references another field of the same model. When set the slug field we be automatically set to a slugified version of the referenced field.#155