Update MAX_MAP_LIMIT to 100,000 in OpenAPI documentation #157
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.
Update MAX_MAP_LIMIT to 100,000 in OpenAPI documentation
Summary
This PR updates the maximum value for the
limitparameter in the map endpoint from 30,000 to 100,000 across three OpenAPI specification files in the documentation repository. This brings the OpenAPI documentation in sync with the actual code implementation in the main firecrawl repository, whereMAX_MAP_LIMITis already set to 100,000 in both v1 and v2 types.ts files.Files updated:
api-reference/v1-openapi.json- Updated limit maximum from 30,000 to 100,000v1/api-reference/v1-openapi.json- Updated limit maximum from 30,000 to 100,000v1/api-reference/v2-openapi.json- Updated limit maximum from 30,000 to 100,000Note: The
api-reference/v2-openapi.jsonfile already had the correct value of 100,000 and did not need updating.Review & Testing Checklist for Human
firecrawl/firecrawlrepo hasMAX_MAP_LIMIT = 100000set inapps/api/src/controllers/v1/types.tsandapps/api/src/controllers/v2/types.ts(I verified this, but please double-check)Notes