Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sort within fetchers? #1

Open
guillep opened this issue Feb 15, 2020 · 0 comments
Open

Sort within fetchers? #1

guillep opened this issue Feb 15, 2020 · 0 comments

Comments

@guillep
Copy link
Owner

guillep commented Feb 15, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant