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
The @turf/boolean-intersects function does not handle cases when the user wants to ignore self intersections.
@turf/boolean-intersects internally uses the lineIntersect function, which already supports an options parameter. However, this flexibility is not currently exposed in @turf/boolean-intersects.
To enhance the functionality and flexibility of @turf/boolean-intersects, I suggest to add a options parameter. This parameter should be passed through to the lineIntersect function, allowing users to leverage the existing capabilities of lineIntersect, including the ability to ignore self intersections or any other options that lineIntersect supports.
To ensure backward compatibility, the options parameter can be added with a default value that maintains the current behavior of @turf/boolean-intersects.
This approach ensures that existing codebases using @turf/boolean-intersects will not be affected by this change, while new and existing users gain the ability to customize the function's behavior to better suit their needs.
The text was updated successfully, but these errors were encountered:
The
@turf/boolean-intersects
function does not handle cases when the user wants to ignore self intersections.@turf/boolean-intersects
internally uses thelineIntersect
function, which already supports anoptions
parameter. However, this flexibility is not currently exposed in@turf/boolean-intersects
.To enhance the functionality and flexibility of
@turf/boolean-intersects
, I suggest to add aoptions
parameter. This parameter should be passed through to thelineIntersect
function, allowing users to leverage the existing capabilities oflineIntersect
, including the ability to ignore self intersections or any other options thatlineIntersect
supports.To ensure backward compatibility, the
options
parameter can be added with a default value that maintains the current behavior of@turf/boolean-intersects
.This approach ensures that existing codebases using
@turf/boolean-intersects
will not be affected by this change, while new and existing users gain the ability to customize the function's behavior to better suit their needs.The text was updated successfully, but these errors were encountered: