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
Some fetchers will retrieve results in a sort of random order.
For example, the selectors of a class, or the instance variables of a class are retrieved in random order. The Hierarchy decorator fetcher ensures that the selectors/ivars of a class will appear before the selectors/ivars of a superclass. However, the fetchers right now do not enforce anything about the selectors/ivars of a single class.
While this works mostly fine for most cases, there are some cases where it looks strange. For example, imagine you're in a method within a test class:
type super se
the completion engine fetches in order #(selector setUp)
However, shouldn't setUp be before selector?
Even if we decide to sort within fetchers, sorting alphabetically may seem fine for some cases and not fine for others.
I leave this here as an open question.
The text was updated successfully, but these errors were encountered:
Some fetchers will retrieve results in a sort of random order.
For example, the selectors of a class, or the instance variables of a class are retrieved in random order. The
Hierarchy
decorator fetcher ensures that the selectors/ivars of a class will appear before the selectors/ivars of a superclass. However, the fetchers right now do not enforce anything about the selectors/ivars of a single class.While this works mostly fine for most cases, there are some cases where it looks strange. For example, imagine you're in a method within a test class:
super se
#(selector setUp)
However, shouldn't
setUp
be beforeselector
?Even if we decide to sort within fetchers, sorting alphabetically may seem fine for some cases and not fine for others.
I leave this here as an open question.
The text was updated successfully, but these errors were encountered: