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
We have a bunch of methods on our model that we would like to expose in the GeoJSON. Currently we had to add a bunch of properties to the model to provide these values (all of these properties just calling into the bound methods already present on the model...).
It would be nice to have the ability to include callable methods with no parameters (that is, only self). Is this something the project maintainers would like to include? Are there any pitfalls / possible conflicts / discouragements to implement this?
The text was updated successfully, but these errors were encountered:
We have a bunch of methods on our model that we would like to expose in the GeoJSON. Currently we had to add a bunch of properties to the model to provide these values (all of these properties just calling into the bound methods already present on the model...).
It would be nice to have the ability to include callable methods with no parameters (that is, only
self
). Is this something the project maintainers would like to include? Are there any pitfalls / possible conflicts / discouragements to implement this?The text was updated successfully, but these errors were encountered: