| --- | --- |
| Bugzilla Link | 561296 |
| Status | UNCONFIRMED |
| Importance | P3 normal |
| Reported | Mar 20, 2020 08:03 EDT |
| Modified | Mar 20, 2020 08:03 EDT |
| Reporter | Hans van der Laan |
Description
This isn't a bug report but quality of life feature request. Also, I'm not really sure if this is the right group for these requests.
Feature: \
At the moment, the Eclipse Query Result explorer orders the patterns alphabetically. It would be useful if you could also order them based on how you ordered them in the VQL file.
Explanation:\
When you write code, you usually group your methods based on shared characteristics. For example, you usually you group your getters/setters somewhere and the other helper methods such as toStrings(), equals(), etc. somewhere else.
I'm not yet very experienced with VQL, however when I write VQL patterns I also tend to group them based on shared characteristics and with a certain ordering in mind. Now, when looking up the results one has to go back and forth between their mental ordering and the alphabetical ordering. This doable for a small amount of queries, but will probably become burdensome when dealing with a large amount of patterns. A good feature would thus be if they could also be ordered based on how they were specified in the loaded VQL file.
| --- | --- | | Bugzilla Link | 561296 | | Status | UNCONFIRMED | | Importance | P3 normal | | Reported | Mar 20, 2020 08:03 EDT | | Modified | Mar 20, 2020 08:03 EDT | | Reporter | Hans van der Laan |
Description
This isn't a bug report but quality of life feature request. Also, I'm not really sure if this is the right group for these requests.
Feature: \ At the moment, the Eclipse Query Result explorer orders the patterns alphabetically. It would be useful if you could also order them based on how you ordered them in the VQL file.
Explanation:\ When you write code, you usually group your methods based on shared characteristics. For example, you usually you group your getters/setters somewhere and the other helper methods such as toStrings(), equals(), etc. somewhere else.
I'm not yet very experienced with VQL, however when I write VQL patterns I also tend to group them based on shared characteristics and with a certain ordering in mind. Now, when looking up the results one has to go back and forth between their mental ordering and the alphabetical ordering. This doable for a small amount of queries, but will probably become burdensome when dealing with a large amount of patterns. A good feature would thus be if they could also be ordered based on how they were specified in the loaded VQL file.