Handling expression in location cast #41
Merged
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.
This pull request introduces enhancements to the
laravel-spatial
package, focusing on adding expression support for theLocationCast
class, modernizing the test suite with PHPUnit attributes, and improving test coverage. Below are the most significant changes grouped by theme:Enhancements to
LocationCast
functionality:Expression
objects in theget()
method ofLocationCast
by introducing a privategetCoordinates()
method. This allows parsing spatial expressions likeST_GeomFromText
to extract coordinates. (src/Casts/LocationCast.php
) [1] [2]Modernization of the test suite:
@test
annotations with#[Test]
attributes across all test methods for compatibility with modern PHPUnit syntax. (tests/HasSpatialTest.php
,tests/LocationCastTest.php
,tests/PointTest.php
) [1] [2] [3]Improved test coverage:
get()
method inLocationCast
correctly handlesExpression
objects and returns aPoint
instance. (tests/LocationCastTest.php
)Documentation updates:
CHANGELOG.md
file to document the new features and changes introduced in version3.0.1
. (CHANGELOG.md
)