If a user accidentally (or not) enters a key with some whitespace around it, they might not notice the whitespace and wonder why their query returned to no data. For example I copy and pasted "amenity" and took a really long time to find the issue of no data getting downloaded.
This PR checks all entered keys for leading or trailing whitespace to catch mistakes like that and raises a warning if found.
If the user really wants to download features with keys that have leading or trailing whitespace they can manually edit the query (says @Gustry).
If a user accidentally (or not) enters a key with some whitespace around it, they might not notice the whitespace and wonder why their query returned to no data. For example I copy and pasted "
amenity
" and took a really long time to find the issue of no data getting downloaded.This PR checks all entered keys for leading or trailing whitespace to catch mistakes like that and raises a warning if found.
If the user really wants to download features with keys that have leading or trailing whitespace they can manually edit the query (says @Gustry).
PS: I did not test the test!