Draft
Conversation
This commit introduces several enhancements to the slugify function, including support for protected words that must always be included in the final slug. It also adds functionality for truncating slugs at a specified maximum length while respecting word boundaries and ensuring protected words are prioritized. Additionally, new test cases have been added to validate these features, ensuring backward compatibility and proper handling of stopwords.
This commit introduces a new test case for the slugify function, specifically validating the handling of multi-token protected words in Chinese. The test ensures that the slug is generated correctly while respecting the protected words, enhancing the robustness of the slugify functionality.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.