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

Provide deprecation message to external users of escaped_path #1138

Merged
merged 2 commits into from Aug 4, 2014

Conversation

JonRowe
Copy link
Member

@JonRowe JonRowe commented Aug 4, 2014

Provide a deprecation for #escaped_path in 2.99 we assumed noone was using the private(ish) API but we were wrong, fixes #1127.

def c._escaped_path(parts, internal = true)
unless internal
RSpec.deprecate("RSpec::Configuration#escaped_path", :replacement => nil)
end
Copy link
Member

Choose a reason for hiding this comment

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

This isn't exactly true. escaped_path needs to be moved out of example_group to the top level if they choose to use it.

Copy link
Member Author

Choose a reason for hiding this comment

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

It's defined on their instance of RSpec::Configuration and it's gone in 3.0.0 hence it's deprecated...

Copy link
Member

Choose a reason for hiding this comment

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

Oh wow, I totally mis-read things. Yep, carry on. LGTM.

@cupakromer
Copy link
Member

@JonRowe thanks for tackling this! Looks good, just one small adjustment.

JonRowe added a commit that referenced this pull request Aug 4, 2014
Provide deprecation message to external users of escaped_path
@JonRowe JonRowe merged commit eee0f7c into 2-99-maintenance Aug 4, 2014
@JonRowe JonRowe deleted the deprecate_escaped_path branch August 4, 2014 22:12
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

2 participants