This release is a pre-release and may not be stable for production use.
gooddata-code-convertors
GoodData AAC YAML / Declarative API code converters, powered by WebAssembly.
Provides bidirectional conversion between AAC YAML format (used by the gdc-analytics-as-code VSCode plugin) and GoodData Declarative API format.
Installation
pip install gooddata-code-convertors
Usage
YAML-to-Declarative functions accept parsed YAML dicts (e.g. from yaml.safe_load),
not raw YAML strings.
import yaml
from gooddata_code_convertors import yaml_metric_to_declarative, declarative_metric_to_yaml
# AAC YAML -> Declarative API
with open("metrics/revenue.yaml") as f:
parsed = yaml.safe_load(f)
declarative = yaml_metric_to_declarative(parsed)
# Declarative API -> AAC YAML
yaml_result = declarative_metric_to_yaml(declarative)
Types: static (_types) vs. runtime-validating (pydantic_models)
Two parallel sets of Python types are generated from the same AAC JSON Schema:
gooddata_code_convertors._types—TypedDicts, re-exported at the package top level (from gooddata_code_convertors import Dashboard). Static typing only, zero runtime cost, zero validation.gooddata_code_convertors.pydantic_models— real Pydantic v2BaseModels (not re-exported at the top level, to avoid name collisions with_types— import from the submodule directly:from gooddata_code_convertors.pydantic_models import Dashboard). Use these when you need actual runtime validation of a payload, e.g.Dashboard.model_validate(payload).
Gotcha: shared string-pattern fields (e.g. every entity's id) are wrapped in their own
RootModel[str] class in pydantic_models rather than being plain str — access the value
via .root (e.g. dashboard.id.root). This is a deliberate trade-off: collapsing them into
plain str fields breaks import entirely, because pydantic-core's Rust regex engine can't
compile this schema's negative-lookahead patterns once collapsed. _types' TypedDicts are
unaffected (Dashboard["id"] is a plain str there, since TypedDict has no runtime pattern validation
to trip over).
Available Converters
YAML -> Declarative API
yaml_dataset_to_declarativeyaml_date_dataset_to_declarativeyaml_metric_to_declarativeyaml_visualisation_to_declarativeyaml_dashboard_to_declarativeyaml_plugin_to_declarativeyaml_attribute_hierarchy_to_declarative
Declarative API -> YAML
declarative_dataset_to_yamldeclarative_date_instance_to_yamldeclarative_metric_to_yamldeclarative_visualisation_to_yamldeclarative_dashboard_to_yamldeclarative_plugin_to_yamldeclarative_attribute_hierarchy_to_yaml
Utilities
build_afm_execution
1 maintainer
Release files for gooddata-code-convertors 11.60.0a0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gooddata_code_convertors-11.60.0a0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / gooddata_code_convertors-11.60.0a0-py3-none-any.whl
| Download URL | gooddata_code_convertors-11.60.0a0-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
523123e64e001a5c603487446012677a3fecc1eeb209335df50cde454f4e11b7
|
|
BLAKE2b-256 checksum How to use checksums |
11dad5958b071ea9dc13ff1f5896733757423ff3e1b2aa9617e3a789e8748c07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency log
