Docs: clearer description for booleanOverlap #2133
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mfedderly
approved these changes
Jun 28, 2021
|
The docs are updated by @rowanwins occasionally. I think its on his list to update sometime soon. |
This was referenced Jul 10, 2021
1 task
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a line explaining booleanOverlap in a more layman-friendly way.
This is my first PR for this project so please feel free to suggest improvements to the PR structure etc.
Do I need to run
npm run docsso that they update? I tried doing this but it rewrote all the READMEs and made them empty, so I've only committed the changed source file instead.resolves #2072
npm testat the sub modules where changes have occurred.npm run lintto ensure code style at the turf module level.