-
Notifications
You must be signed in to change notification settings - Fork 2
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
Properties values should not be limited to String #430
Comments
I get your point. To simplify things, this library currently exports every value in its string representation. Lines 245 to 268 in c4dfe27
|
# [1.8.0-alpha.1](v1.7.0...v1.8.0-alpha.1) (2025-02-22) ### Features * keep value types ([60f9d95](60f9d95)), closes [#430](#430)
🎉 This issue has been resolved in version 1.8.0-alpha.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Does this suit your needs? |
Looks great, thanks! Just please include |
# [1.8.0-alpha.2](v1.8.0-alpha.1...v1.8.0-alpha.2) (2025-02-24) ### Features * derive PartialEq, PartialOrd for Value ([#430](#430)) ([65b7cbb](65b7cbb))
Now it is perfect for me. Thank you! Feel free to close this issue. PS: version should be 2.0.0 if you follow semantic versioning 😉 |
I appreciate that |
# [2.0.0](v1.7.0...v2.0.0) (2025-02-25) ### Features * derive PartialEq, PartialOrd for Value ([#430](#430)) ([65b7cbb](65b7cbb)) * **docs:** update feature description ([d1430c9](d1430c9)) * keep value types ([60f9d95](60f9d95)), closes [#430](#430) ### BREAKING CHANGES * **docs:** previous commits contain a breaking behavior for the next release, because properties are now an enum Value instead of string types
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Property value in MVT can be also number or bool.
The text was updated successfully, but these errors were encountered: