Setup Bazel build for Doxygen API reference #6
Labels
Comments
Horolsky
added a commit
that referenced
this issue
Jan 17, 2025
Generate API reference with local doxygen outside of the Bazel build TODO: remove after #6
Horolsky
added a commit
that referenced
this issue
Jan 23, 2025
* Move the source code from internal repo * Refine package structure * Refactor exceptions * Add initial Python package with dummy driver app * Add initial pyproject.toml for packages/py with Flit build * Add initial tox.ini for packages/py with dummy UT * Update SECURITY.md * Add development status to README * Refine Reflection API and update documentation * Remove unconfigured hermetic_cc_toolchain from Bazel build (see #5) * Add a temp Doxygen script Generate API reference with local doxygen outside of the Bazel build TODO: remove after #6 * Cleanup code and add doxygen docs * Refine namespaces and move internals into detail ns * Remove redundant traits and metafuncs * Move precise template to decor ns * Add doxygen docs. Some trivial metafuncs omitted. * Refactor few templates Breaking: * Move json_from and dejsonize from reflect to main ns * Refine packages directory structure Move * packages/cxx => zmbt-framework/backends/cxx * packages/py => zmbt-framework/cli * Enable parameters nesting in the Expressions - close #10 * Add .bazelversion and build instructions to README * Add minimal documentation for Environment - close #4 Add doxygen docs to Environment interfaces and update docs/environment.md. Interfaces for internal functionality left undocumented - they should be separated from the API in future. * Fix expression keywords issues and add cartesian prod alias - Fix code generation issues - Fix aliases for bitwise ops - add U+00D7 alias for cartesian * Refine JsonNode @ token behavior and remove non-const at * Address code review comments - minor fixes --------- Signed-off-by: Horolsky <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TODO(@Horolsky) elaborate the issue
The text was updated successfully, but these errors were encountered: