You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 14, 2018. It is now read-only.
Sure, I don't see why not... hmm. Would there be a case where you have a Component you don't have the class reference for? Yes, actually if the Component is in another application. Though in that case, you would not be using a Context from your application to create it.
There must be a use case why that constructor exists. I'm not sure when ComponentName(context, string) is generally used, or if it is merely a convenience method. It does result in one less function call since it does not need to call getName() on the class to get the String value.
Shrug I'd lean towards not including the string constructor unless I am missing a general use case where this would be useful.
What do you think about a simple extension for creating
ComponentName
instances using aContext
?The text was updated successfully, but these errors were encountered: