|
|
 Filtering Lists by Text Property value
| Issue Type: |
Status: |
Priority: |
Date Submitted: |
Votes: |
| Enhancement |
More Info Required |
Medium |
Sat 19th Mar 2016 |
2 votes
 |
| |
| Found in version: |
Last Updated: |
Completed in version: |
Date Completed: |
Track Changes: |
| 5.0.34.1 |
Sun 20th Mar 2016 |
|
|
Log In |
| |
| ElliotM | | Sat 19th Mar 2016 05:36 |
Right now only the State property can filter a list by its values, the other properties pretty much act like selection properties - the item has it and is included, or it doesn't and is excluded.
I would like to be able to filter a group of objects by their articles, adjectives, and/or nouns. As a hypothetical, let's say I wanted a list of every object that had the word "magical" in it's adjective property field or a list of every object that had the word "map" as one of its nouns.
The syntax could be like the one state properties use:
Everything.Article("your").List
Everything.Adjective("magical").List
Everything.Noun("map").List |
| |
| Campbell | | Sat 19th Mar 2016 09:47 |
| In practical terms, wouldn't it be better to use properties (e.g. Magical etc) and filter on those? Although Everything would be a useful function. |
| |
| ElliotM | | Sun 20th Mar 2016 05:49 |
Maybe that wasn't the best illustration, as not all objects that are magical might have it as an adjective. However, you are planning to allow us to modify the article, adjective, and noun properties with tasks, right? I just thought it would be nice to also be able to filter by them.
Consider this example: What if objects can be given colors in their adjective field? Would it make more sense from an efficiency standpoint to be able to filter by the adjective field or to maintain a large state property for filtering that also records that information? Why have information in two places like that if you don't need to?
I guess this enhancement request isn't that essential, but I thought it would be good addition. |
|
