5 posts tagged with "Linting"

We've added new validation and linting rules that flag API entity names exceeding 100 characters in OpenAPI specifications. Names exceeding 100 characters now produce an Error-severity violation that blocks Code Generation, Docs Generation, and Portal Generation.

We've expanded the openapi-v3-apimatic-linting,openapi-v3-codegen-linting, openapi-v3-standard-linting, and openapi-v3-standards-validation rulesets with new linting and validation rules covering Pagination, Webhooks, and Callbacks.

This release delivers comprehensive code quality improvements to our Python SDKs. Generated SDKs now produce Ruff-compatible code that adheres to PEP 8 and PEP 257 style guidelines.

Key outcomes:

• Cleaner, more maintainable SDK code that follows modern Python best practices, with properly formatted docstrings, organized imports, and consistent styling
• CI/CD integration ready with included ruff.toml configuration for automated linting

The improvements span string literal consistency, import organization, docstring formatting, line length management, and formatter-friendly structure. Where linting rules could potentially impact existing consumer code, they are intentionally bypassed to preserve behavior.

Zero-Downtime Upgrade

• No action required. These improvements maintain full backward compatibility with existing SDK implementations. No breaking changes are included.
• Simply regenerate your Python SDKs to take advantage of these enhancements

We've introduced a new OpenAPI linting ruleset for Agentic Tools generation.

As part of our efforts to improve existing format-specific validation, we are now introducing validators for Swagger v2.0 and OpenAPI v3.0 specifications.