Allow params to work for Global Exposure
See original GitHub issueIn 1.3 resolver-links where removed. According to the migration guide “reducers” are recommended as a replacement. Unfortunately the reducer function has only access to the plain object and it doesn’t seem possible to get access to the filters of the query or to define filters for the sub query.
E.g. this was possible with links
MyCollection.createQuery({
some: 1,
other: {
$filter({filters, params}) {
filters.searchTerm = params.searchTerm
}
}
})
The filters where passed through to the links resolver function (second parameter).
And chance to get the possibility of accessing filters or passing through parameters in any way down to reducer functions?
Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (12 by maintainers)
Top Results From Across the Web
How to use photographic exposure controls in Corona for 3ds ...
Use global exposure : If "Use simple exposure" is selected in Render Setup > Camera, then exposure is defined in there. · Use...
Read more >Information exposure through query strings in url
Information exposure through query strings in URL is when sensitive data is passed to parameters in the URL. This allows attackers to obtain...
Read more >A Global Exposure Model for GAR 2015, UNEP-GRID
This report describes how a global exposure database was generated for the quantification of the exposure, to support the earthquakes and cyclones probabilistic ......
Read more >K72880030: Positional parameters for a URL (15.1.x and 16.1.x)
Log in to the Configuration utility. · Go to Security > Application Security > URLs > Allowed URLs > Allowed HTTP URLs. ·...
Read more >how to handle optional http query params
When invoked the direct service using SOAP UI with/without query params, its working fine. I have added the query parameters under http request...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I understand I will look into this.
Sidenote: this bug is also present for the
$postFilter()
function. According to docs:$postFilter(results, params) { ... return results }
, but for meparams
is always undefined, just like in the reducers as stated above.