-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Escape question marks in URLs #558
Conversation
This one is the fix for #547 |
Is there a way we could apply a more general URL sanitization step? |
@jpsim for example? Are there any other issues related to the URLs sanitization? |
Yes, there have been issues with Windows file names before too, which is why I'd like to implement a general solution to URL escaping rather than hardcoding this case, without addressing possible others. |
@jpsim like this one #361? So I suggest by simply adding handlign for these characters, and handle them in tests in https://github.com/realm/jazzy-integration-specs/tree/master/misc_jazzy_features |
That seems fine to me! |
Since the original solution proposed in this PR was rejected in favour of a more generic one, I'm going to close this PR. Feel free to re-open or file a new PR with the new/preferred solution. |
Source Kitten output could have question marks in document names when parsing Swift sources. Since we cannot use question marks in URLs, we need to escape them with some adequate characters sequence.
q
was added to represent question mark, and-
was added since no potential function name can have dashes in it