| name | code-review |
|---|---|
| description | PR review for Contentstack Python CDA SDK — public API, Stack, HTTP layer, tests. |
- API: New or changed
Stack/ content-type / query / entry methods documented;contentstack/__init__.pyexports updated if needed. - Version:
__version__incontentstack/__init__.pyaligned with release strategy for breaking changes. - HTTP:
https_connection.py/controller.pychanges keep retry and timeout behavior predictable. - Tests:
pytest tests/passes; extendtests/when CDA behavior changes. - Secrets: No tokens in repo;
config.pyremains local-only when it holds real credentials.
- Exported
Stack, ContentType, Query, asset/entry helpers match README and consumer expectations;contentstack/__init__.py__all__stays accurate when exports change. - Docstrings on
Stackand key public methods when behavior or options change.
- Avoid breaking
Stack.__init__signatures or method chains without a semver strategy; document migration for breaking changes (setup.py/__version__).
- Changes to
requests, retry behavior, orHTTPSConnectionshould stay consistent withcontentstack/controller.pyandurllib3Retryusage instack.py.
- Tests hit the live CDA when using
configcredentials; extendtests/when request/response behavior changes. Do not commit new secrets.
- No hardcoded tokens in source or docs; no logging of api keys, delivery tokens, preview, or management tokens.