feature: handle nested objects when getting attribute values#2235
feature: handle nested objects when getting attribute values#2235johnnyblasta wants to merge 4 commits intomasterfrom
Conversation
|
I was going to test this but I'm not clever enough : / In the issue you wrote
{
"detaljplan": {
"objektidentitet": "0490dfc9-8dxf-4992-bcbb-9ed8ab6137d9",
"beteckning": "2281K-DP-xx",
"namn": "xxxx",
"status": "laga kraft",
"typ": "detaljplan",
"datumLagakraft": "1991-12-05",
"kvalitet": {
"korrigeradeGranser": true,
"kontrolleratPlaneringsunderlag": false
},
"anvandbarhet": "god"
}
}So if an attribute of a geojson feature has a prop like |
|
Below is a complete GeoJSON from the OGC API Features from Lantmäteriet's service for NGD Detaljplan, which you can use for testing purpose. |
|
Seems to function as intended, i.e I can specify Maybe each method inside should be documented and the parameters described via |
|
I let Visual Studio Code do the DocTypes thing for the JSDoc so I don't rely know if it's good or not :) |
|
To sum what we discussed during our meeting then, merge with proposed similar function "searchjson" https://github.com/origo-map/origo/pull/2224/files#diff-73a377a3fa3092fb30d691c5c3145af68f00519db030398cef9a51111b1566d5 , as for jsdocs for getContent I'm thinking this pr doesn't necessarily need to include them? |
Tested using the "searchjson" function, but found it quiet different and had difficulty implementing using that function. |
Closes #2234