Skip to content
Back to pull request #351

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

Sign in to view logs

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 #441

This job was skipped