Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deno_http can not provide custom property extractor #28420

Open
vanppo opened this issue Mar 7, 2025 · 0 comments
Open

deno_http can not provide custom property extractor #28420

vanppo opened this issue Mar 7, 2025 · 0 comments
Labels
embedder Embedders using deno crates to build their own runtime rather than using Deno itself

Comments

@vanppo
Copy link

vanppo commented Mar 7, 2025

After #28317, it is not possible to provide custom property extractor for deno_http.

This probably due to the Feature unification of cargo, so my default-features = false does not work as expected.

# Cargo.toml
[package]
name = "runtime"
version = "0.1.0"
edition = "2024"

[dependencies]
deno_http = { version = "0.192.0", default-features = false }
deno_runtime = { version = "0.202.0", features = ["transpile"] }
$ cargo tree -f "{p} {f}"
runtime v0.1.0 (/Users/vanppo/Downloads/runtime) 
├── deno_http v0.192.0 default,default_property_extractor
└── deno_runtime v0.202.0 deno_ast,transpile
    └── deno_http v0.192.0 default,default_property_extractor (*)
@marvinhagemeister marvinhagemeister added the embedder Embedders using deno crates to build their own runtime rather than using Deno itself label Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
embedder Embedders using deno crates to build their own runtime rather than using Deno itself
Projects
None yet
Development

No branches or pull requests

2 participants