Closed zachdaniel closed 4 years ago
Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
---|---|---|---|---|---|
lib/span.ex | 7 | 8 | 87.5% | ||
<!-- | Total: | 7 | 8 | 87.5% | --> |
Totals | |
---|---|
Change from base Build 7182e4ff-b3ad-45af-bc71-390b20d7b463: | 2.2% |
Covered Lines: | 213 |
Relevant Lines: | 252 |
Maybe we should think about how to mark this as deprecated so that we could get it merged, and then remove it when we decide we're ready for 3.0 (assuming that ever happens).
@GregMefford I don't really think there is a good way to mark the existing behavior as deprecated. I think we'd just need a major version change to include it. No one will accidentally upgrade, and we can make it really big on the readme. Beyond that, there isn't much we can do.
This is old/stale, and I'm not really making any behavioral changes to Spandex except in reaction to issues.
If you are using the
private
key for tags, you will need to switch to usingtags
, or the appropriate top level tag attribute likesql_query
orhttp
.This is also 1 considered a breaking change because it is likely/possible that implementations were relying on this behavior. If you aren't leveraging tags, or if your spans aren't very deep in general than you most likely don't need to deal with this.