| name | contentstack-utils |
|---|---|
| description | Public API—Utils, Options, RTE/embedded, GQL, editable tags; JS parity; no bundled HTTP client. |
- Implementing or changing RTE/HTML rendering, embedded resolution, GQL, or editable-tag behavior.
- Updating
README.md/changelog.rst/setup.pyfor user-visible behavior. - Assessing semver impact of
__init__.pyexports and public classes.
Utils—contentstack_utils.utils:render_content,render, embedded/RTE resolution; subclassesAutomate.Options—contentstack_utils.render.options: rendering configuration passed intoUtilsmethods.- Editable tags —
entry_editable:addEditableTags,addTags,getTag; also exposed asUtils.addEditableTags/Utils.addTags/Utils.getTagfor parity.
- Embedded / RTE — JSON and HTML paths through
UtilsandAutomate; metadata viaMetadata. - Styles —
convert_styleand embedded StyleType / ItemType where applicable. - GQL —
GQLingql.pyfor GraphQL-oriented HTML/helpers.
contentstack_utils/__init__.py__all__and exports must match README examples and intended surface (Utils,Options,GQL,Automate, embed types, tag helpers).- JS parity — where methods mirror the JS utils SDK, keep parameter names and behavior consistent unless a documented breaking change.
- Avoid breaking
Utils/Options/ tag helpers without a semver plan; bumpsetup.pyversionfor user-visible changes.
lxmlusage stays bounded to parsing/rendering paths; note any newinstall_requiresin README / changelog if added tosetup.py.
- This package does not ship HTTP clients or tokens.
- Consumers often use
contentstack.Stack(Contentstack package) to fetch entries, thenUtils.render/Utils.render_content— keep README examples accurate.
- Content Delivery API
skills/python-style/SKILL.md,skills/framework/SKILL.md