Fix maximum crawl count #470
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
|
Could you remove all unnecessary changes from this PR. Those |
|
Ack... sorry thought I had |
Akilez
force-pushed
the
fix-maximum-crawl-count
branch
from
737b0ab to
db515bf
Compare
|
There that should be better... ? |
|
Thank you! |
BoGnY
pushed a commit
to BoGnY/laravel-sitemap
that referenced
this pull request
Jan 26, 2023
This reverts commit 6527aa9.
freekmurze
pushed a commit
that referenced
this pull request
Jan 26, 2023
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Currently the
laravel-sitemapplugin has no way to natively set the maximum crawl count due to a call that uses the wrong (old?) method name on theSpatie\Crawler\Crawlerclass.