Open meh9 opened 9 years ago
hi @meh9 , would you please give me a bit more details: what is this flatten property supposed to do? Also how can I test it?
The flatten
property flattens the structure of automagically loaded groups.
To illustrate and help you with testing I made an init file you can drag and drop in a Terria app (NM, AREMI, etc) that shows the different behaviour:
Thanks @meh9 :+1:
Just a thought: in terms of consistency with other CatalogGroup types (eg Ckan and Socrata), the way to express this might be:
"groupBy": "none"
had a try using
"groupBy": "none"
but it doesn't seem to flatten the data.
Created branch issue725 to port the property, please let me know if you have any other ideas @stevage
Sorry, I meant, instead of calling the property "flatten", calling it "groupBy" with those semantics. We have a bit of a problem with similar properties being implemented on many different catalog items, with not enough inheritance.
Using groupBy
instead of flatten
.
When groupBy
=== "none"
, then the structure of the group is flattened.
@stevage , would you like me to change the existing flatten
property of wms-getCapabilities
into groupBy
as well?
That would break any existing sites that use "flatten". Let's talk with @kring when he's back.
Hey, @kring is back now. What do you think?
groupBy
sounds fine. We can support backward compatibility by using the defaultUpdaters
thing.
It would be great to be able to use the "flatten" property on "esri-mapServer-group"s just like we can on "wms-getCapabilities" groups. That would make configs like the following look much better in the data catalogue: