Opentelemetry-specification: Why are we using such a long name as StatusCanonicalCode?
From https://github.com/open-telemetry/opentelemetry-specification/pull/1067#discussion_r500495896.
Another question is: Are there non-canonical status codes?
bogdandrutu
All 4 comments
I think this should be renamed to just Status (or StatusCategory) after #966. The current enum is not canonical and I also don't know if we want to call it a code.
Oberon00
on 6 Oct 2020
I don't think this is a blocker for GA but if we intend to change that (and from the 馃憤 on here we seem to have some consensus), we should do so before GA. It should be a simple find-and-replace for SIGs that have already adopted the new Status model and otherwise it would go well along with that change.
arminru
on 7 Oct 2020
I'd prefer to settle this before GA since the names may be part of the API. In that case changing the names will break the API.
tigrannajaryan
on 7 Oct 2020
from the issue triage mtg today, need a decision on this whether to have it
andrewhsu
on 9 Oct 2020
Related issues
cijothomas
路
3Comments
carlosalberto
路
4Comments
XSAM
路
3Comments
rochdev
路
6Comments
naseemkullah
路
5Comments
Most helpful comment
I think this should be renamed to just Status (or StatusCategory) after #966. The current enum is not canonical and I also don't know if we want to call it a code.