Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Class prefixes on iOS
See original GitHub issueIt’s common practice for iOS libraries to include some kind of class prefix for name spacing, eg: on React Native, RCTx. Maybe WIXx here?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
What is class prefix in Xcode - Apple Community
The class prefix is a prefix for class files Xcode generates when you create a project or class file. An example of a...
Read more >Swift Framework Prefix? - ios
Two-letter prefixes like these are reserved by Apple for use in framework classes. You should avoid two-letter prefixes, as all such prefixes ......
Read more >The NS prefix should only be used by Apple · Issue #57
In order to keep class names unique, the convention is to use prefixes on all classes. You'll have noticed that Cocoa and Cocoa...
Read more >What does the "NS" prefix to a class name mean in iOS?
It stands for NextSTEP, the operating system that Steve Jobs (caused to be) built after he was evicted from Apple. Objective-C and the ......
Read more >Namespacing
Class Prefixes ; MK, MapKit ; MP, MediaPlayer ; NK, NewsstandKit ; NS, Foundation, AppKit, CoreData.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@talkol There is currently an interest to bring Interactable to Expo, @brentvatne is leading the efforts I believe, this prefixes issue is what is blocking the library from being included as a part of the Expo SDK. I am not sure on how difficult it is to make the changes needed, I would submit a PR if I could, but I am not an expert on the matter. Just wanted to point out that adding Interactable to Expo would not only benefit the library itself, but also it adds a great value to those who are developing on top of Expo.
You’re right. Since I’m aiming eventually to PR into the core (once the issues are ironed out and people are happy with the API), what do you think about using the core namespace? (RCT)