1. Feedback
  2. Blazor
  3. 37145

Welcome to the Blazor feedback portal. We’re happy you’re here! If you have feedback on how to improve the Blazor, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

Document the subset of GeoJSON you support, and provide proper error messages

The documentation for the Maps component suggests that GeoJSON is supported in full generality. (It does not make this claim outright, but support for GeoJSON features is mentioned in many places, and an incautious reader may come away with that impression.)

In fact, you do not support GeoJSON in full generality. Not only that, but if a user attempts to use GeoJSON features that you do not support, the error messages you generate are not the least bit helpful.

In particular:

  • You do not support the Line or LineString geometry types. The only content on your site that makes this explicit is forum posts. Line and LineString are valid GeoJSON geometry types and if you aren't going to support them, you should make that clear.
  • You do not support GeoJSON files that aren't Features contained in a FeatureCollection.

To elaborate in the second bullet point: The following is a valid GeoJSON document:

{"type":"Feature","geometry":{"type":"Polygon","coordinates":[[[0,0],[10,0],[0,10],[0,0]]]}}

But you don't accept it. You only accept GeoJSON documents that are of type "FeatureCollection". In order to get the above GeoJSON to work, one has to wrap it in a gratuitous FeatureCollection. This is not documented anywhere on your site that I could find; I had to work it out for myself.

If the user attempts to use GeoJSON that is valid per the GeoJSON specification, but which uses GeoJSON features that you arbitrarily fail to support, your component does not generate helpful error messages. It generates error messages that are obscure and do not remotely hint at what the user needs to do to get things working.

Given that you do not support naked GeoJSON feature documents, I would expect that if I were to try to use one, I should get an error message that says something like "Plain GeoJSON features are not supported. Please provide a FeatureCollection". That is only an example; a wide range of possible acceptable wordings could be imagined. The actual errors you see in the browser console are as follows:

  • Uncaught (in promise) Error: System.InvalidOperationException: Operation is not valid due to the current state of the object. (followed by a stack trace)
  • Unhandled exception rendering component: Operation is not valid due to the current state of the object. (followed by a stack trace)

These errors are no help whatsoever to the user in figuring out what they are doing "wrong".