Added HasGeometryScropes trait and a sample implementation of within #86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I was hoping to contribute to this repository. Could you please tell me if you like this structure?
If so I can add some more functions and make a test suite for them.
The scopes design is inspired from: https://github.com/grimzy/laravel-mysql-spatial/blob/master/src/Eloquent/SpatialTrait.php
I figured it would be nice to put these scopes in a separate file, or what do you think?
Also, pondered, what if scopes could accept strings like 'App\Park', tablenames, instance id or something else to make the actual queries inside of the database. To use the scopes with a WKT insertion does not seem optimal? Fine if it is some BBOX, but what if it has thousands of vertexes. Any guidance of these kind of questions would help alot.
Finally please be gentle as this is my first serious PR :)