Skip to content

Conversation

@jrafanie
Copy link
Member

@jrafanie jrafanie commented Nov 8, 2024

@jrafanie jrafanie force-pushed the fix-uri-1-0-1-warnings branch from f1e35b0 to 56ed15b Compare November 20, 2024 20:15
@jrafanie jrafanie closed this Dec 10, 2024
@jrafanie jrafanie reopened this Dec 10, 2024
@miq-bot
Copy link
Member

miq-bot commented Mar 5, 2025

Checked commit jrafanie@56ed15b with ruby 3.1.5, rubocop 1.56.3, haml-lint 0.51.0, and yamllint
1 file checked, 0 offenses detected
Everything looks fine. ⭐

@miq-bot miq-bot added the stale label Jun 9, 2025
@miq-bot
Copy link
Member

miq-bot commented Jun 9, 2025

This pull request has been automatically marked as stale because it has not been updated for at least 3 months.

If these changes are still valid, please remove the stale label, make any changes requested by reviewers (if any), and ensure that this issue is being looked at by the assigned/reviewer(s).

url_parm = parse_questionmark.post_match if parse_questionmark.present?
url_parm = parse_ampersand.post_match if parse_ampersand.present?
encoded_url = URI::DEFAULT_PARSER.escape(url_parm)
encoded_url = URI::RFC2396_PARSER.escape(url_parm)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Closing, they must have fixed/pulled/pushed 1.0.1 as the warnings are gone now in 1.0.1 and 1.0.4

irb(main):001> require 'uri'
=> true
irb(main):002> URI::DEFAULT_PARSER
=> #<URI::RFC3986_Parser:0x0000000121efb998>
irb(main):003> URI::VERSION
=> "1.0.4"
irb(main):004> URI::PATTERN::UNRESERVED
=> "\\-_.!~*'()a-zA-Z\\d"

@jrafanie
Copy link
Member Author

Not needed anymore

@jrafanie jrafanie closed this Oct 15, 2025
@jrafanie jrafanie deleted the fix-uri-1-0-1-warnings branch October 16, 2025 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants