DRF 2.4.3 breaks drf-GIS

[joaoponceleao]

As the title says.
Specifically, when using getJSON, leaflet.js throws an error of invalid json.
Everything works fine when going back to DRF 2.4.2.

[nemesifier]

The failing build message is not nice: https://travis-ci.org/djangonauts/django-rest-framework-gis/jobs/34644034
Will look into it asap.

[sephii]

Not sure if it's related but I ran into a bug when using DRF 2.4.3 where Point fields would always be output as their textual representation (POINT(... ...)) instead of their structured representation. That's because of encode/django-rest-framework@e437520, which changed the way the mappings between fields and their representation is done.

I tried adding the following to MapGeometryField and it solved the problem. Not sure it's the best way to do it though. HTH.

class MapGeometryField(dict):
    def __contains__(self, key):
        if not super(MapGeometryField, self).__contains__(key):
            return issubclass(key, django_GeometryField)

        return True

[nemesifier]

@sephii thanks for the suggestion, very helpful, I'm looking into it right now.

[nemesifier]

i could not find any other solution which I judged better, your solution seems to work, let's wait for the travis build to finish... if it's successful I'll issue a new release right away

[nemesifier]

New release issued: https://github.com/djangonauts/django-rest-framework-gis/releases/tag/v0.6
Fixed. Thanks!