PowerShell Studio Feature Requests

Feature requests, product enhancement ideas, and other product-specific suggestions.

`Configuration` Per-Project Settings

Bosparan, Dec. 17, 2017Under Review

Copied from this thread

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.

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.

So here's the proposal:

  • 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!

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

You must be logged in to make a comment on a feature request. Click here to log in now.

Make a Request

You must be logged in to make a feature request. Click here to log in now.
PowerShell Studio
 PrimalScript
 VersionRecall
 PowerShell HelpWriter
 PowerShell ModuleManager
 WMI Explorer
 PrimalXML
 PrimalSQL
 iPowerShell
 iPowerShell Mac
 iPowerShell Android
 SAPIEN Website