Draft
Conversation
This commit introduces new features to the slugify function, allowing for the preservation of specified protected words and the removal of stopwords during slug generation. It includes tests for various scenarios, such as max length truncation, word boundary handling, and backward compatibility. Additionally, command-line argument parsing is updated to support protected words, enhancing the overall slugification process.
…ords This commit updates the slugify function to guarantee the presence of protected words, even when absent in the input text or when truncation occurs. It includes new test cases to validate these behaviors, ensuring that protected words are prioritized in the slug generation process.
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.