on 11-27-2023 9:19 AM
When developing CAP CDS for Node.js I regularly had Custom Handlers in which I needed to read some part of the req.query object to make some other backend calls, sometimes I even had to modify the pre-generated queries so that they would properly work on a backend.
Let's take a look on what changed with CDS(here version 7.4.0)
As you can see, req.query.SELECT only contains a from section. Some other params like filter, limit and orderBY are not in this query object, but in Symbol(Original). -Why?
This makes developing with CAP a bit more confusing and more difficult for me.
For Example last week I had accessed a filter with req.req.query.$filter and tried to parse those filter back to CQL, so I could modify and then reattach it to the query parameters. But this doesn't seem like a good Practice
Are there new Best Practices when working with req.query in Custom Handlers using the newer CDS versions? How can I Access req.query.Symbol(Original) in my custom handlers (something like req.query.Symbol(Original) or req.query.['Symbol(Original'] doesnt work)?
Any Guidance or reference to documentation would be massively helpful.
The view in the debugger is misleading you. You can access all the information you need as properties. Try the following and you will see that information is available.
let {from,columns,where,orderBy,limit} = req.query.SELECT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you're totally right. i've never noticed this. Why would the debugger even hide the fields even though they are still there
i've actually wrote this abomination of code to solve it temporarily but this will now go away of my production code hopefully forever
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.