Modify ↓
Opened 16 years ago
Closed 16 years ago
#3562 closed defect (invalid)
type=way doesn't work, but type:way does
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | Cc: |
Description
type=(node|way|relation) doesn't work but and type=(node|way|relation) does. The two should be equivalent.
Attachments (0)
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
I *guess*, you are referring to the filter, maybe to the search function, but I can't tell for sure from your report. Could you please elaborate what you did, what happened and what you expected to happen?
comment:3 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | needinfo → closed |
Urgh, here I am filing succinct bug reports thinking they're unambiguous but evidently there's some new features negating my assumptions.
In any case it was the search engine and this was my mistake. I thought the new = operator should also have the same type=* magicness as type:*.
Note:
See TracTickets
for help on using tickets.
type=way and type:way are different things. type=way means there is tag type with value way. type:way means the element is way.