feat(core): linter looser description length #175
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
guoqqqi
approved these changes
Aug 22, 2024
bzp2010
changed the title
nic-chen
approved these changes
Aug 22, 2024
guoqqqi
approved these changes
Aug 22, 2024
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.
Description
API7 supports a longer description field than 256 bytes, while ADC sets a smaller limit for this field. This affects some use cases.
This PR relaxes the 256 length limit to 64 * 1024 = 65536 bytes.
Note that APISIX does not change its position on the 256 length limit at this time, so the Admin API still uses 256 bytes as the length limit when you use the APISIX backend. This limit may change later, but it is not a commitment.
Checklist