Add maxLiteralStringLength as a configuration property #1656
+284
−72
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.
We introduce a new configuration property
maxLiteralStringLengththat fixes #1416 and #1655.The property can be set either in the serverSettings (e.g.
.vscode/settings.json):{ "basedpyright.analysis.maxLiteralStringLength": 100 }or in the
pyproject.toml:or in the
pyrightconfig.json:{ "maxLiteralStringLength": 100 }Know issues
It looks like we can't control the render-length of completion suggestions, which is unfortunate. However, even though completion suggestions are still truncated after 50 characters, the effective value on auto-complete respects the configuration property.