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.

Sign up for GitHub

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

fix(fs): Apply requireLiteralLeadingDot config #1585

Merged
merged 3 commits into from
Jul 25, 2024
Merged

fix(fs): Apply requireLiteralLeadingDot config #1585

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
22eae4a
fix(fs): Apply requireLiteralLeadingDot config
FabianLars Jul 25, 2024
0e545f7
fix deserialization
FabianLars Jul 25, 2024
807fa8b
reword changefile [skip ci]
FabianLars Jul 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changes/fix-fs-apply-leading-dot-config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"fs": patch
---

Fixed an issue that caused the plugin to ignore the `requireLiteralLeadingDot` config.
2 changes: 1 addition & 1 deletion plugins/fs/src/commands.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -854,7 +854,7 @@ pub fn resolve_path<R: Runtime>(
.chain(global_scope.denies().iter().map(|e| e.path.clone()))
.chain(command_scope.denies().iter().map(|e| e.path.clone()))
.collect(),
require_literal_leading_dot: None,
require_literal_leading_dot: app.fs_scope().require_literal_leading_dot,
},
)?;

Expand Down
1 change: 1 addition & 0 deletions plugins/fs/src/config.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@
use serde::Deserialize;

#[derive(Deserialize)]
#[serde(rename_all = "camelCase", deny_unknown_fields)]
pub struct Config {
/// Whether or not paths that contain components that start with a `.`
/// will require that `.` appears literally in the pattern; `*`, `?`, `**`,
Expand Down