Add example of env expansion with non-standard integer notation #3959
Labels
area:configuration
Related to configuring the SDK
triage:accepted:ready
Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
Comments
4 tasks
trask
added
triage:deciding:community-feedback
|
cc @open-telemetry/configuration-maintainers |
1 task
jack-berg
pushed a commit
that referenced
this issue
May 8, 2024
Updates #3959 ## Changes Adds example for using an integer in hexadecimal notation. The intention is to show the difference when quoting vs not quoting and make explicit that quoting means keeping the original representation (we already have the `true` example but this one has two different representations). I think this is already implied by the text so this is only a change in the example. * [x] Related issues #3959, part of #3963 --------- Co-authored-by: Robert Pająk <[email protected]>
|
Fixed by #3975 |
github-project-automation
bot
moved this from Spec - Accepted
to Completed Projects
in 🔭 Main Backlog
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this issue
Oct 31, 2024
…y#3975) Updates open-telemetry#3959 ## Changes Adds example for using an integer in hexadecimal notation. The intention is to show the difference when quoting vs not quoting and make explicit that quoting means keeping the original representation (we already have the `true` example but this one has two different representations). I think this is already implied by the text so this is only a change in the example. * [x] Related issues open-telemetry#3959, part of open-telemetry#3963 --------- Co-authored-by: Robert Pająk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider the case where the variable
HEX_VALUEis set to0xdeadbeef, and a configuration field such as:where
string_fieldhas typestringon the JSON schema. What should its value be? I am not sure which of the following would be correct per the spec:0xdeadbeef(preserving the original presentation format)3735928559(representing with a standard base 10 format)Having an explicit example of this case on the spec would be useful to understand it.
The text was updated successfully, but these errors were encountered: