GeometryField changed from tuple to list

[stianjensen]

I see that you updated your tests here to compare the output of the GeometryField with a list instead of a tuple. I also had to do this in my tests when upgrading to 0.12 today.

https://github.com/djangonauts/django-rest-framework-gis/pull/138/files#diff-e37466d2e4622040c1152104aede1b55L524

Is this an intentional change that is worth documenting in the changelog?

[auvipy]

@nemesisdesign

[nemesifier]

hey @stianjensen, not intentional on my side when I accepted the PR but worth documenting in the changelog if you spent time on it

[gregseb]

I apologize, in hindsight this was worth special mention by me as soon as I edited a test that wasn't created in the same PR.

Looking back, #138 wasn't quite as simple as adding support for GeometryCollections. It altered DRF-GIS to leverage the GEOSGeometry.geojson formatter instead of building its own GeoJSON.

Perhaps the understating of the changes brought by #138 is part of the issue here?

It's GEOSGeometry.geojson that uses a list rather than a tuple.

[nemesifier]

If anybody would like to improve the change log so that this information is more evident, please do :-)