Rename things for Ably #8
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using the regexp /(?<!ART)SR(?!unLoop)(?!ange)/. And then handle the consequent changes that this requires - namely, renaming files and updating the README.
This in particular affects the framework bundle identifiers, so that our fork can coexist alongside the Facebook version.
|
Oops, I got the issue number wrong in the branch name and PR description. It should be 949, not 969. I've replaced this PR with #9. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's new
This is a preparatory step on the road to compiling SocketRocket directly into ably-cocoa, as described in this comment on ably/ably-cocoa#969.
It changes the naming so that things look like Ably code - specifically, replacing the
SRnamespace withARTSR.With this change, an application could in theory use both our SocketRocket fork and its own version of SocketRocket without experiencing any issues.
Notes
Normally, in a fork, a big rename like this would be something to be very careful about because it makes it very difficult to merge further changes from upstream. But the upstream project is well and truly dead, so I don't think we need be concerned.
Questions for reviewers
Cartfilein ably-cocoa to point to this changed version, and I had 3 failing tests when running the tests inside Xcode 12. But I don't know whether that's to be expected or not. And I also pushed it to a private CocoaPods repository and checked that I was able to compile an app that uses this version of the library.What's next