fix: More readable error with unsortable index column

[saulshanabrook]

Fixes #1567 by raising a better error message pointing out when a column has an unsortable index.

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 90.18%. Comparing base (28ee3da) to head (efecb13).

Files	Patch %	Lines
...filing/report/structure/variables/render_common.py	50.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1568      +/-   ##
===========================================
- Coverage    90.19%   90.18%   -0.02%     
===========================================
  Files          195      195              
  Lines         6394     6396       +2     
===========================================
+ Hits          5767     5768       +1     
- Misses         627      628       +1     

Flag	Coverage Δ
py3.8-ubuntu-22.04-pandas	90.18% <50.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[alexbarros]

hi @saulshanabrook, I was checking the error, and it seems the confusing message has to do with the profiling version. In the latest version the error is a bit less confusing, it still is a stack trace, but indicates a bit better the cause.
In the end the cause of the error is that ydata-profiling currently fails while trying to infer the geopandas.Point since it is not part of the supported types.
It still able to generate the report if you define the type to categorical using the type_schema parameter and it will display the categorical statistics for the column.

report = ProfileReport(gdf, type_schema={"geometry": "categorical"})

also, since the error is captured early, it don't get to render pipeline to trigger the validation you added. The correct message in this case needs to be added to the type inference (i.e. infer types), and since it depends on a external lib (visions) so the improvement would likely be added to visions instead.

I will be closing both the PR and the linked issue in this case.