solution to implement url-safe strings (#347) #514
Closed
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.
Description:
This pull request introduces an approach to generate URL-safe strings, as discussed in Issue #347. It implements a new
--url-safe
(or-u
) flag for thenanoid
CLI, enabling users to generate IDs that are safe to use in URLs by avoiding problematic characters, such as underscores at the end of strings.Key Changes:
--url-safe
flag has been added to the command-line interface, allowing users to specify that the generated ID should be URL-safe.customAlphabet
Function: ThecustomAlphabet
function has been updated to accept aurl_safe
parameter, making it easy for users to generate URL-safe IDs when needed.Motivation:
This approach addresses issues related to trailing underscores and other characters that can cause problems in URLs, such as rendering issues or broken links in Markdown and web applications. By enabling the generation of URL-safe IDs, the solution enhances compatibility and reliability when working with URLs.
Key Note:
This is not yet considered a complete solution, but rather an approach to how this can be implemented. Feedback is welcome for further improvement.