Fix gis contrib geometry resolution when using different source (ref #989)

[submarcos]

Try to implement bugfix to #989

[submarcos]

@tfranzel Hi. Can you take a look at this ?

[submarcos]

@tfranzel Hi. I'm blocked because drf-spectacular doesnt work with django.contrib.gis in some cases describe in #989. Can you take a look at this PR to fix and release ? thank you very much

[Copilot]

Pull request overview

This PR addresses issue #989 by fixing how GeoFeatureModelSerializer’s geo_field is resolved when the serializer field’s source does not directly match a model field name (e.g., source="aoi.geometry"), preventing KeyError during schema generation.

Changes:

• Update GIS contrib schema generation to resolve geometry model fields via follow_field_source(...) using the serializer field’s source path.
• Add a regression test case covering a GeoFeatureModelSerializer whose geo_field points to a serializer field with a different source.
• Update the expected OpenAPI snapshot to include the new test route/schema.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
drf_spectacular/contrib/rest_framework_gis.py	Fixes geometry model-field resolution by following the serializer field’s source path.
tests/contrib/test_rest_framework_gis.py	Adds a new GeoFeature serializer scenario to exercise “geo_field name != model field name”.
tests/contrib/test_rest_framework_gis.yml	Updates expected schema snapshot for the new endpoint/component.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.