You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the new major release, I propose the removal of the Summarizable interface along with its toArray method. This decision stems from my belief that all models should instead implement the JsonSerializable interface, thereby returning a GeoJSON compatible result where feasible.
The usage of arrays in this context seems antiquated and unnecessarily complex, hence it doesn't align with the direction of our project. I anticipate that the removal of these features won't be a significant loss for the users. However, I welcome any thoughts and potential concerns about this proposed change.
Exporting in GeoJSON is a must. This library could then act as a GPX to GeoJSON converter (like some others - not much - but with the other features like the stats that make this library charming).
As part of the new major release, I propose the removal of the
Summarizable
interface along with itstoArray
method. This decision stems from my belief that all models should instead implement theJsonSerializable
interface, thereby returning a GeoJSON compatible result where feasible.The usage of arrays in this context seems antiquated and unnecessarily complex, hence it doesn't align with the direction of our project. I anticipate that the removal of these features won't be a significant loss for the users. However, I welcome any thoughts and potential concerns about this proposed change.
Originally posted by @Sibyx in #67 (comment)
The text was updated successfully, but these errors were encountered: