"Smart" query route (/query) - MAPCO-4638

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
api, backend

Research direction

Start by locating the existing route definitions and the handlers for /tile and other specific routes. Define the regex-based matching behavior for /query, verify that matching requests proxy to the intended route, and add coverage for representative query patterns and unmatched requests.

Written by the indexing model from the issue text.

Description

enhancement In Design

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.

Dominant language
TypeScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MapColonies/geocoding

All issues in MapColonies/geocoding

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.