[PSS] Per Project options / options file

Post feature requests, product enhancement ideas, and other product-specific suggestions here. Do not post bug reports.
Forum rules
Do not post any licensing information in this forum.
This topic is 6 years and 11 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
Locked
Bosparan
Posts: 290
Last visit: Fri Oct 08, 2021 11:59 am

[PSS] Per Project options / options file

Post by Bosparan »

Hi Guys,

I'm currently working on multiple open source projects and one thing is driving me nuts!
I've got lots of flexibility in configuring PowerShell Studio - haven't found something that comes close so far - but it's all global settings.

Idea:
- Per project options
- All settings default to the global config, but can individually be overridden for a project.
- The per-project settings (or modifications from the default options) should be stored separately in an options file.
- Projects have associated options files, that are part of the project!

Most Open Source projects have style guides, and few are identical among each other. This has led me to having to reconfigure PSS when switching between projects.
Being able to do so flexibly would be great! Even better, by sharing the options as option files, I can maintain the settings to adhere to style guidelines as part of the project, making it ...
a) Easier to distribute across team-members
b) More attractive for other team-members to also use PSS

Cheers,
Fred
DevinL
Posts: 1098
Last visit: Tue Jun 06, 2017 9:15 am

Re: [PSS] Per Project options / options file

Post by DevinL »

Thank you for your suggestion, I've filed an internal feature request and if we get some information, we'll be sure to post it here.
DevinL
SAPIEN Technologies, Inc.
This topic is 6 years and 11 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
Locked