# This package is deliberately named `ztracing` and not `lumbridge-ztracing-shim`.
#
# A `[patch]` entry can only replace a package with one of the SAME NAME, so the
# name is load-bearing: the root manifest's
# `[patch."https://github.com/zed-industries/zed.git"]` table redirects the
# `ztracing` that `gpui` and `sum_tree` ask for at this directory, and Cargo
# matches the two by package name. The directory keeps the `lumbridge-` prefix
# every other crate here has so that a reader browsing `crates/` can see whose
# code it is; `src/lib.rs` explains why the package underneath answers to a
# different name.
[package]
name = "ztracing"
description = "A no-op stand-in for Zed's GPL-licensed ztracing, so Lumbridge's build graph stays Apache-2.0"
version = "0.1.0"
edition.workspace = true
rust-version.workspace = true
license.workspace = true
repository.workspace = true
publish = false

# A proc-macro crate, because the only symbol the graph reaches for is an
# attribute macro. Nothing else can live in a crate declared this way, which is
# the point: an upstream revision that starts using `ztracing::Span` or
# `ztracing::info_span!` fails to compile here rather than quietly resolving.
[lib]
proc-macro = true

# No dependencies. `syn` and `quote` would only be needed to parse an item this
# macro then reassembles unchanged; returning the input `TokenStream` untouched
# is both correct and three crates cheaper.
[dependencies]

[lints]
workspace = true