Improve findinstances handling of Swift subclasses #219
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.
Calling
findinstances
currently requires the exact class name. For classes implemented in Swift, the name includes the module name, for exampleSuperKit.DuperClass
. This change allowsfindinstances
to be called with simply the class name (DuperClass
in the previous example).Note: This change does handle the case where more than one module contains a class by that name. For example, if two modules each define a class named
User
, then runningfindinstances User
will list instances of both classes.This pull request also includes a few other small improvements.