Skip to content

Fudgefile.psd1 support #70

@jayvdb

Description

@jayvdb

Continuing from #59

.psd1 support would have lots of advantages. It doesnt need to replace the Fudgefile[.json] support. It should be additional, for people who have needs which make simple json undesirable. This also avoids backwards compatibility issues.

Re the "trailing comma" problem mentioned in issue #59, I see them used a lot, e.g.

https://github.com/PowerShell/PSScriptAnalyzer/blob/master/Engine/Settings/CodeFormattingOTBS.psd1

I hope it isnt a standard linting rule that they should be added.

Also another possible negative is that lint rules for PS typically require alignment of '=', which means adding a new property with a longer length means that other lines need to be adjusted to insert more whitespace. Whitespace additions are not nearly as bad, as git includes options to ignore whitespace changes, even when tracing through the blame history.

The reason why linting rules are relevant is the standard linter doesnt have good ability to ignore some files. PowerShell/PSScriptAnalyzer#1230

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions