Skip to content

fix: Pavex always uses a public path to refer to public items, even if they are defined in a private module #564

fix: Pavex always uses a public path to refer to public items, even if they are defined in a private module

fix: Pavex always uses a public path to refer to public items, even if they are defined in a private module #564

Triggered via pull request October 22, 2024 17:29
Status Success
Total duration 37s
Artifacts

deny.yml

on: pull_request
Matrix: cargo-deny check
Fit to window
Zoom out
Zoom in