Change Details

Hi, I'm currently using 2 extensions, GeoData and Maps, both of which define the #coordinates parser function, and Maps seems to take priority over GeoData when using the function in pages. Ideally I would be able to write something like #Maps.coordinates or #GeoData.coordinates to avoid this issue. Would this feature possible to implement in this (the ParserFunction) extension?

Hi, I'm currently using 2 extensions, GeoData and Maps, both of which define the #coordinates parser function, and Maps seems to take priority over GeoData when using the function in pages. Ideally I would be able to write something like #Maps.coordinates or #GeoData.coordinates to avoid this issue. Would this feature possible to implement in this (the ParserFunctions) extension?

Hi, I'm currently using 2 extensions, GeoData and Maps, both of which define the #coordinates parser function, and Maps seems to take priority over GeoData when using the function in pages. Ideally I would be able to write something like #Maps.coordinates or #GeoData.coordinates to avoid this issue. Would this feature possible to implement in this (the ParserFunctions) extension?