throwErrorOnExtraParameters is not documented
See original GitHub issueThe following appears in several examples:
throwErrorOnExtraParameters: true
It is missing in the generated documentation, but is documented in the code as:
/** * If true then if the request JSON has extra parameters exceptions will be thrown. Otherwise the * information will be logged. */
The documentation is not quite accurate, see discussion below.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Complying With Medical Record Documentation Requirements
If there is no response to the request for medical records, the CERT may also make a telephone call to solicit the documentation....
Read more >MapFish Print 3 Documentation - Configuration
This section lists the available configuration components that can be used in the YAML configuration file. Example config.yaml. throwErrorOnExtraParameters: ...
Read more >Sample config.yaml with all available options #600 - GitHub
For instance keys like throwErrorOnExtraParameters and transparentTileErrorColor only appear in the examples and certain configurations and ...
Read more >Populating second subreport without data adapter - json ...
The problem is very simple to explain: I am not able to populate the 2nd ... throwErrorOnExtraParameters: true templates: A4 portrait: ...
Read more >Issues printing OSM basemap using MapFishPrint 3
getSerializedLayers( mapComponent, function(layer) { // do not print the ... throwErrorOnExtraParameters: true templates: A4 portrait: ...
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 Free
Top 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

Ok, let’s not mix up the 2 things, if you want to create a new issue for the changed behavior, here is the example:
It doesn’t seem to work like that, e.g. I would have expected an error to be thrown with the flag set when passing an attribute
"foo": "bar"in theattributesObject of the pdf generation request, since I didn’t specify afooattribute in myconfig.yaml, but no error was thrown.As I said, I’m happy with the fixed doc, if anyone else is not, feel free to create an issue.