Home > Blockchain >  same base url with different functionalities nodejs
same base url with different functionalities nodejs

Time:09-11

    app.get('/api/v3/app/events', async function (req, res){
            try {
                let unique_id=req.query.id
                console.log(unique_id)
              
                 database.collection('event').findOne(ObjectId(unique_id),function(err,data){
                    if(err){
                        res.json({error:"no data found with specified id"})
                    }
                    console.log(data)
                    res.json(data)}
                )
              
            } catch (error) {
                console.log("internal error")
                res.json({error:error})
            }
    
        })
    
    
    
     app.get('/api/v3/app/events', function(req,res) {
            try {
                let limit=parseInt(req.query.limit)
                let page =parseInt(req.query.page)
                console.log(database.collection('event').find().sort({$natural: -1}).limit(limit).skip(page-1).toArray((err, result) => {
                    console.log(result);
                })
                )
                
                
            } catch (error) {
                console.log(error)
                return res.json({error:"internal error "})
            }
            
        })

I have to perform these functionalities with same base url i.e '/api/v3/app/events'. Please help . I am successful as I change the names of endpoints, but keeping them same , I gets null and undefined on the console

CodePudding user response:

I'm not sure why do you need both to use same URL, but you have two choices either use a single endpoint with both of the logics. The other option would be to use the next middleware based on the id query param like this:

app.get('/api/v3/app/events', async function (req, res, next){
    if (!req.query.id) {
        next();
        return;
    }

    // Rest of your endpoint logic
}

Each endpoint in Express is considered as middleware. This means that response won't be sent back, but calling the next() middleware instead and allow other middlewares to be executed. You can use same if or modify it based on your login.

  • Related