As part of the agreed architecture, We would like to add a /query route which will enable users, instead of querying specific route to get their data, to be able to query one "smart" route which will give them their wanted result. At first, we need to create a route which based on regexes, this route will "proxy" to the right desired route. For example, if user sent "tile ...", the route will proxy it to /tile route.
As part of the agreed architecture, We would like to add a /query route which will enable users, instead of querying specific route to get their data, to be able to query one "smart" route which will give them their wanted result. At first, we need to create a route which based on regexes, this route will "proxy" to the right desired route. For example, if user sent "tile ...", the route will proxy it to /tile route.