-
Notifications
You must be signed in to change notification settings - Fork 31
Add mojo-toml v0.5.1 - Native TOML parser & writer #196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Package: mojo-toml v0.3.0 A native TOML 1.0 parser for Mojo with zero Python dependencies. Features: - Complete TOML 1.0 syntax support - 96 comprehensive tests ensuring reliability - Nested tables, dotted keys, duplicate detection - Clear error messages with line/column context - Performance: 26μs for simple parses, 2ms for real files Repository: - GitHub: https://github.com/DataBooth/mojo-toml - Release: https://github.com/DataBooth/mojo-toml/releases/tag/v0.3.0 - License: MIT Testing: Package includes test_package.mojo which validates: - Simple key-value parsing - Integer and array parsing - Nested table structures - Dotted key functionality All 96 tests pass in the source repository. Sponsored by DataBooth (https://www.databooth.com.au/posts/mojo)
Updates mojo-toml from v0.3.0 to v0.5.0 with full TOML 1.0 compliance and partial TOML 1.1 support. Major changes since v0.3.0: - Complete TOML 1.0 specification (array-of-tables, alt number bases) - Partial TOML 1.1 support (\xHH and \e escapes) - 168 tests (up from 96) - Comprehensive benchmarking system - Pre-commit hooks fixed - TOML writer with round-trip fidelity Release: https://github.com/DataBooth/mojo-toml/releases/tag/v0.5.0 Co-Authored-By: Warp <agent@warp.dev>
|
Looks like there is an error in your recipe, also I believe the mojo version you would be looking for is |
|
Hi - thanks @bgreni - as a bit of an aside see also #195 - I think this might be a modular-community repo issue that causes some errors too? Actually I think the macOS build failure was specifically because the CI couldn't find tag v0.5.0 when the package version declared 0.5.1 - this is now resolved. Looking more closely - the main issue is that the recipe schema expects: Ok so version should be pinned to latest stable (25.7)? I am now doing the following with the version: which is apparently what other packages do. Furthermore made the following enhancements to improve my build reliability: Fixed recipe schema compliance issues and standardised Mojo version management across all of my 5 mojo packages including • ✅ Schema fixes: Changed test: → tests:, doc_url → documentation, dev_url → repository per rattler-build requirements |
- Update source tag from v0.5.0 to v0.5.1 - Update license from MIT to Apache-2.0 (matches upstream change) Co-Authored-By: Warp <agent@warp.dev>
- Add context with version and mojo_version variables - Change from 'mojo >=25.1' to 'mojo-compiler =0.25.7' - Use pin_compatible() for runtime dependency Co-Authored-By: Warp <agent@warp.dev>
- Change 'test:' to 'tests:' with script block - Change 'doc_url' to 'documentation' - Change 'dev_url' to 'repository' Fixes recipe parser errors per modular-community schema. Co-Authored-By: Warp <agent@warp.dev>
|
Actually, still doing some further work to make it more bulletproof - will comment when ready for review |
Adds mojo-toml v0.5.1 - Native TOML 1.0 parser and writer for Mojo.
Changes from previous PR #193:
recipes/mojo-toml/image.png) for builds.modular.com display per reviewer requestPackage features:
[[section]]syntaxRepository: https://github.com/DataBooth/mojo-toml
CodeQL:
Supersedes #193