Expose MapviewAPI for programatic consumption of Search Providers
As mentioned in #138 I've created a API class that can be used to expose various parts of the API to be then consumed by other plugins like QuickAdd
I did some refactoring of the geosearch files to make it slightly easier to consume. If you'd like me to undo / change some of that please let me know.
Haven't tested completely yet but wanted to get something out there as I worked on it.
I could really use this feature, is it still planned?
To me it would be sufficient if there was just a search method I could use from templater to get the location of a search string
I could really use this feature, is it still planned?
To me it would be sufficient if there was just a search method I could use from templater to get the location of a search string
I sure wouldn't object if someone added this functionality, but this specific PR didn't converge eventually, and in my own list of priorities this is currently not very high :-/
@esm7 I'm happy to give this another go but I never heard back from you on the above review bits.
Actually, re-reading the old code, I'm much less opinionated against the solution you provided. Would you mind giving it a refresh so it works with the latest version?