A HOCON value resolver that's capable of doing value type detection. It should be able to detect Integer, Boolean and finally string based on the value. It's a must have in order to have an ability to merge with JSON having values in those types
Motivation and Context
HOCON supports variables resolving from system properties. However, by design it always wraps it as String. However, we're using JSON extensively to configure verticles. Verticle implementations are looking forward for values in type of Integer (e.g. port) or boolean, so there is a need to be able to properly inject those values.
Screenshots (if appropriate):
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
I hereby agree to the terms of the Knot.x Contributor License Agreement.
marcinczeczko
commented
6 years ago
Description
A HOCON value resolver that's capable of doing value type detection. It should be able to detect Integer, Boolean and finally string based on the value. It's a must have in order to have an ability to merge with JSON having values in those types
Motivation and Context
HOCON supports variables resolving from system properties. However, by design it always wraps it as String. However, we're using JSON extensively to configure verticles. Verticle implementations are looking forward for values in type of Integer (e.g. port) or boolean, so there is a need to be able to properly inject those values.
Screenshots (if appropriate):
Types of changes
Checklist:
I hereby agree to the terms of the Knot.x Contributor License Agreement.