Skip to content
This repository was archived by the owner on Jan 19, 2025. It is now read-only.

Usage-based Filters #496

Closed
lars-reimann opened this issue May 18, 2022 · 0 comments · Fixed by #538
Closed

Usage-based Filters #496

lars-reimann opened this issue May 18, 2022 · 0 comments · Fixed by #538
Assignees
Labels
enhancement 💡 New feature or request

Comments

@lars-reimann
Copy link
Member

lars-reimann commented May 18, 2022

Is your feature request related to a problem? Please describe

Since the editor does not have the usage data available, it's not possible to filter the API elements using usage data.

Desired solution

Add two filters:

  • is:used
  • is:useful

to filter the tree view and show only the respective API elements. The default state of the filter box should also be to only show used and useful API elements.

Possible alternatives

  • usages:>3
  • usefulness:>10 (meaning: for classes/functions identical to usages:>10, for parameters: there are more than 10 usages of values of than the most common one)

Operators: :<, :<=, : (equality), :>=, :>

Additional context (optional)

@lars-reimann lars-reimann added the enhancement 💡 New feature or request label May 18, 2022
@lars-reimann lars-reimann moved this to Backlog in API Editor May 18, 2022
@lars-reimann lars-reimann self-assigned this Jun 3, 2022
@lars-reimann lars-reimann moved this from Backlog to In Progress in API Editor Jun 3, 2022
@lars-reimann lars-reimann linked a pull request Jun 3, 2022 that will close this issue
@lars-reimann lars-reimann moved this from In Progress to Ready for Review in API Editor Jun 3, 2022
Repository owner moved this from Ready for Review to ✔️ Done in API Editor Jun 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement 💡 New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant