Process URL in the same way as Express does to get request parameters in a get command

By -

I want to be able to get the parameters from a uri string in the exact same way as Express does. I can do it with regex or other string methods, but then I have a risk that it is not interpretted the same way as Express. I would prefer a way that even if Express has a bug and a URI gets interpretted wrongly, that the function does that as well.

I have Ajax commands that execute a specific get/post command and use the referer to know where they originated eg. req.headers.referer which would be something like http://localhost:3000/data/theme-chalkboard/black

I have a non standard get in Express, for example:

app.get('/data/theme-:theme/:piece', (req, res, next) => {
// server code
}

Where the parameters in question are:

{
  theme: "chalkboard",
  piece: "black"
}

However I have other parts that also have similar incorporated variables within the route. The reason for this is because the route gets dynamically created and updated as the website is used by oneself and others. Because of this, I might need information on one page to be able to query it correctly on another.

From the referer I get a URI string eg.

http://localhost:3000/data/theme-chalkboard/black 
or 
http://localhost:3000/hg-1000

Then I want to be able to first determine which of the following get commands it matches:

app.get('/data/theme-:theme/:piece', (req, res, next) => {});
or 
app.get('/hg-:gameId', (req, res) => {});

And lastly get the parameters in a JSON format, eg.

{
  "theme": "chalkboard",
  "piece": "black"
}

or

{
  "gameId": "1000"
}

If I have to add custom code to first determine each type of command and then to get the parameters as well it is still fine, as this would be similar to the regex idea that I am currently considering. The problems with this solution is that my regex might not always interpret the URI exactly like Express would and I would have to do this for each of the routes that could get a command. I would prefer a generic solution that acomplishes this if it exists.



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more