configerator-development

To validate Configerator .cconf files locally, run a local configerator build using the `conf build` command. This processes your bespoke Python dialect configurations and materializes the output, which must be committed alongside your changes.

The best way to lint Configerator configurations is by running the `conf lint` command. This checks your .cinc, .cconf, and .mcconf files for correctness against the custom import system and CI hooks, ensuring your submission passes validation.

Configerator build failures with import errors often stem from its bespoke Python dialect, which is compiled via exec() with a custom import system and builtins. Debugging requires understanding that standard Python import rules do not apply to .cinc and .cconf files.

To submit Configerator configuration changes, use the `conf submit` command with a designated mutation ID. This process ensures your validated and linted .cconf and .cinc file modifications are properly tracked and integrated into the system.

No, Configerator does not use standard Python syntax. It uses a bespoke Python dialect compiled via exec(), featuring a custom import system and builtins specifically designed for handling materialized configs within the .cinc, .cconf, and .mcconf file formats.

Debugging Configerator build failures is limited by its non-standard Python execution model via exec() and custom builtins. Developers must account for materialized configs and CI hooks, as traditional Python debugging tools may not correctly interpret the custom import system.