Skip to content
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

Temporary fix for UTF-8 bug in addressable #79

Merged
merged 2 commits into from Feb 3, 2016

Conversation

roback
Copy link
Member

@roback roback commented Feb 1, 2016

Temporary fix for #62.

Related to sporkmonger/addressable#224

Used the code in #62 (comment) as inspiration, but I had to modify it so we didn't have to call addressable.display_uri twice.

@walro
Copy link
Contributor

walro commented Feb 1, 2016

I think this looks good

raise
end

private :new, :internal_parse, :to_addressable_uri, :addressable_display_uri
Copy link
Collaborator

Choose a reason for hiding this comment

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

what about splitting this line to multiple lines, so next time we get the nice diff :)

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure. What is the best way of doing that?

private :new,
  :internal_parse,
  :to_addressable_uri,
  :addressable_display_uri

# or

private :new
private :internal_parse
private :to_addressable_uri
private :addressable_display_uri

For the second one we wouldn't have to add a , on the last line when adding a symbol, so I think that one looks best :).

Copy link
Contributor

Choose a reason for hiding this comment

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

I like the second one (easier to remove/add line).

Copy link
Contributor

Choose a reason for hiding this comment

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

I think the second one too

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yeah, sure let's go with the second one :)

Copy link
Member Author

Choose a reason for hiding this comment

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

@roback
Copy link
Member Author

roback commented Feb 3, 2016

I'll create a new gem version after #78 is merged too.

roback added a commit that referenced this pull request Feb 3, 2016
…tf-8

Temporary fix for UTF-8 bug in addressable
@roback roback merged commit f9fd65b into master Feb 3, 2016
@roback roback deleted the fix/62/invalid-byte-sequence-in-utf-8 branch February 3, 2016 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants