Currently, when requesting JSON for a gallery, forceDCR is ignored. This is because the request has to be categorised as a "remote render" for DCAR JSON to be provided. However, this JSON is provided by frontend, not DCAR, so it's not accurate to call it a "remote render".
This change creates a separate case, apart from the "remote render" logic, to handle DCAR JSON for galleries.
Note: Prior to #27556 it would still have been possible to get DCAR JSON, because forceDCR would have categorised the request as a "remote render". However, as mentioned above, this is not a "remote render", so the solution is to make the change here rather than reverting or altering that PR.
All deployment options
- [Deploy build 3299 of `dotcom:frontend-all` to CODE](https://riffraff.gutools.co.uk/deployment/deployAgain?project=dotcom%3Afrontend-all&build=3299&stage=CODE&updateStrategy=MostlyHarmless&action=deploy)
- [Deploy parts of build 3299 to CODE by previewing it first](https://riffraff.gutools.co.uk/preview/yaml?project=dotcom%3Afrontend-all&build=3299&stage=CODE&updateStrategy=MostlyHarmless)
- [What's on CODE right now?](https://riffraff.gutools.co.uk/deployment/history?projectName=dotcom%3Afrontend-all&stage=CODE)
Keep an eye on the deploy dashboard&_a=(description:'',filters:!(),fullScreenMode:!f,options:(darkTheme:!f,useMargins:!f),panels:!((gridData:(h:4,i:'4',w:6,x:6,y:0),id:'735f9ce0-4a04-11e7-9f15-395e2d1c9b1f',panelIndex:'4',type:visualization,version:'6.2.4'),(gridData:(h:4,i:'5',w:6,x:0,y:0),id:b9249830-4a03-11e7-91e8-2fbfd59c38bb,panelIndex:'5',type:visualization,version:'6.2.4'),(gridData:(h:4,i:'7',w:6,x:0,y:4),id:ac507b90-4a0f-11e7-9f15-395e2d1c9b1f,panelIndex:'7',type:visualization,version:'6.2.4'),(gridData:(h:4,i:'9',w:6,x:6,y:4),id:a5f78860-4ad2-11e7-9930-73b4968e85d8,panelIndex:'9',type:visualization,version:'6.2.4')),query:(language:lucene,query:(query_string:(analyze_wildcard:!t,query:'stage:PROD%20NOT%20app:preview'))),timeRestore:!f,title:'Frontend%20PROD%20Deploy',viewMode:view)) 📉
Keep an eye on the deploy dashboard&_a=(description:'',filters:!(),fullScreenMode:!f,options:(darkTheme:!f,useMargins:!f),panels:!((gridData:(h:4,i:'4',w:6,x:6,y:0),id:'735f9ce0-4a04-11e7-9f15-395e2d1c9b1f',panelIndex:'4',type:visualization,version:'6.2.4'),(gridData:(h:4,i:'5',w:6,x:0,y:0),id:b9249830-4a03-11e7-91e8-2fbfd59c38bb,panelIndex:'5',type:visualization,version:'6.2.4'),(gridData:(h:4,i:'7',w:6,x:0,y:4),id:ac507b90-4a0f-11e7-9f15-395e2d1c9b1f,panelIndex:'7',type:visualization,version:'6.2.4'),(gridData:(h:4,i:'9',w:6,x:6,y:4),id:a5f78860-4ad2-11e7-9930-73b4968e85d8,panelIndex:'9',type:visualization,version:'6.2.4')),query:(language:lucene,query:(query_string:(analyze_wildcard:!t,query:'stage:PROD%20NOT%20app:preview'))),timeRestore:!f,title:'Frontend%20PROD%20Deploy',viewMode:view)) 📉
Currently, when requesting JSON for a gallery,
forceDCR
is ignored. This is because the request has to be categorised as a "remote render" for DCAR JSON to be provided. However, this JSON is provided by frontend, not DCAR, so it's not accurate to call it a "remote render".This change creates a separate case, apart from the "remote render" logic, to handle DCAR JSON for galleries.
Note: Prior to #27556 it would still have been possible to get DCAR JSON, because
forceDCR
would have categorised the request as a "remote render". However, as mentioned above, this is not a "remote render", so the solution is to make the change here rather than reverting or altering that PR.